Skip to content
This repository has been archived by the owner on Jul 20, 2022. It is now read-only.

seth account create myalias --wait causes segmentation violation #37

Closed

Conversation

mithunshashidhara
Copy link

After starting up seth, during account creation
segmentation violation occurs.

Resolves: STL-1241

Signed-off-by: mithunshashidhara mithunx.shashidhara@intel.com

Copy link
Contributor

@vaporos vaporos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Accidental permission change from 644 to 755 in this PR.

After starting up seth, during account creation
segmentation violation occurs.

Resolves: STL-1241

Signed-off-by: mithunshashidhara <mithunx.shashidhara@intel.com>
@mithunshashidhara
Copy link
Author

corrected file permissions, please check.

@dplumb94 dplumb94 self-assigned this Jun 26, 2018
@@ -81,7 +81,8 @@ func (args *AccountCreate) Run(config *Config) error {
if args.Nonce == "" {
nonce, err = client.LookupAccountNonce(priv)
if err != nil {
return err
nonce = 0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This hides any other error message that would come from client.LookupAccountNonce. We need to check the Account.Nonce value in client.LookupAccountNonce and make sure that a valid value is returned instead of nil

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there are log messages inside client.LookupAccountNonce for all the error scenarios that i have encountered so far, only when account creation nonce is not generated from rest-api, in other scenarios i do see nonce. this was the only solution i could come up with.

if body.Data == nil {
err := fmt.Errorf("Rest API GET received improper response")
return nil, err
} else {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still fixing the same problem?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, its the same problem which you had commented earlier, sorry i messed up git during update of commit, so i created a new PR

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@knkski yes this issue is fixed, i will close this PR, Thanks

@knkski
Copy link
Contributor

knkski commented Aug 15, 2018

@mithunshashidhara: This should've been fixed by #42. Are you still encountering this issue?

@mithunshashidhara
Copy link
Author

reported issue fixed in PR #42

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants