Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Account signing fix #1111

Merged
merged 6 commits into from
Oct 19, 2017
Merged

Account signing fix #1111

merged 6 commits into from
Oct 19, 2017

Conversation

frozeman
Copy link
Contributor

This should fix the transaction signing for custom network IDs. Please test.

@coveralls
Copy link

coveralls commented Oct 13, 2017

Coverage Status

Coverage increased (+0.03%) to 85.593% when pulling 2132923 on accountSigningFix into 2db8312 on 1.0.

@naddison36
Copy link
Contributor

I would like to test this as I'm trying to sign locally before sending raw transaction to a remote node. What's the best way to get npm to install from this accountSigningFix branch?

@frozeman
Copy link
Contributor Author

Use in your package json the the git branch rather than the version number: https://stackoverflow.com/questions/39732397/install-specific-branch-from-github-using-npm

@naddison36
Copy link
Contributor

@frozeman I tried adding "web3": "git://github.com/ethereum/web3.js#accountSigningFix" to my package.json but I got the following error

npm ERR! Darwin 16.7.0
npm ERR! argv "/Users/nick/.nvm/versions/node/v6.11.4/bin/node" "/Users/nick/.nvm/versions/node/v6.11.4/bin/npm" "update"
npm ERR! node v6.11.4
npm ERR! npm  v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! [email protected] postinstall: `lerna bootstrap`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script 'lerna bootstrap'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the web3 package,
npm ERR! not with npm itself.

The latest version of the 1.0 branch installs fine "web3": "1.0.0-beta.23"

I seem to be missing something when installing from a branch. Does the branch need to be built?

@frozeman
Copy link
Contributor Author

I updated the eth-lib version to 0.2.5 please re-test.

@naddison36 It should build fine, please check the npm-log, or lerna log for details on your side.

@coveralls
Copy link

coveralls commented Oct 17, 2017

Coverage Status

Coverage increased (+0.03%) to 85.593% when pulling e47b8b5 on accountSigningFix into 2db8312 on 1.0.

@naddison36
Copy link
Contributor

I'm still getting the same error. I've even tried the nuclear option of deleting my node_modules folder and npm cache.

This is the error in npm-debug.log

50149 verbose lifecycle [email protected]~postinstall: PATH: /Users/nick/.nvm/versions/node/v6.11.4/lib/node_modules/npm/bin/node-gyp-bin:/Users/nicholasaddison/Documents/workspaces/open-bank-token/node_modules/web3/node_modules/.bin:/Users/nick/Documents/workspaces/open-bank-token/node_modules/.bin:/Users/nick/.nvm/versions/node/v6.11.4/bin:/Users/nick/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
50150 verbose lifecycle [email protected]~postinstall: CWD: /Users/nick/Documents/workspaces/open-bank-token/node_modules/web3
50151 silly lifecycle [email protected]~postinstall: Args: [ '-c', 'lerna bootstrap' ]
50152 info lifecycle [email protected]~postinstall: Failed to exec postinstall script
50153 verbose unlock done using /Users/nick/.npm/_locks/staging-0ee530199745d5d9.lock for /Users/nick/Documents/workspaces/open-bank-token/node_modules/.staging
50154 silly rollbackFailedOptional Starting
50155 silly rollbackFailedOptional Finishing
50156 silly runTopLevelLifecycles Finishing
50157 silly install printInstalled
50158 verbose stack Error: [email protected] postinstall: `lerna bootstrap`
50158 verbose stack spawn ENOENT
50158 verbose stack     at ChildProcess.<anonymous> (/Users/nick/.nvm/versions/node/v6.11.4/lib/node_modules/npm/lib/utils/spawn.js:33:16)
50158 verbose stack     at emitTwo (events.js:106:13)
50158 verbose stack     at ChildProcess.emit (events.js:191:7)
50158 verbose stack     at maybeClose (internal/child_process.js:920:16)
50158 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
50159 verbose pkgid [email protected]

I don't know where the lerna log is kept

@frozeman
Copy link
Contributor Author

Could you try installing lerna globally before?

@coveralls
Copy link

coveralls commented Oct 19, 2017

Coverage Status

Coverage increased (+0.03%) to 85.593% when pulling 1b0bb5d on accountSigningFix into 66e56b3 on 1.0.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.03%) to 85.593% when pulling 1b0bb5d on accountSigningFix into 66e56b3 on 1.0.

1 similar comment
@coveralls
Copy link

coveralls commented Oct 19, 2017

Coverage Status

Coverage increased (+0.03%) to 85.593% when pulling 1b0bb5d on accountSigningFix into 66e56b3 on 1.0.

@frozeman frozeman merged commit baf384e into 1.0 Oct 19, 2017
@frozeman frozeman deleted the accountSigningFix branch October 19, 2017 13:34
nachomazzara pushed a commit to nachomazzara/web3.js that referenced this pull request Jun 4, 2020
* prepare release

* update eth-lib and added api changes

* updated dist/web3.min.js

* updated eth-lib to 0.2.5

* add warning to the accounts docs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants