This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Sort out web3.js release blocker issues #1504
Comments
This was referenced Dec 8, 2018
Well get them in and make a new release. |
@gnidan Merged these PRs and should be released today. :-) |
This is closable now that there is no outstanding fork. Woot! |
I am having Truffle v5.0.3 which has web3.version as '1.0.0-beta.37' but still getting the below error : roiDevice:Faucet roi$ truffle migrate Can someone please help ?? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are two outstanding issues identified in the latest web3.js that are blocking the Truffle v5 release. We have identified root causes of these and identified solutions for each.
For timeline reasons, and given sufficient confidence in the acceptability of our solutions, we plan to author PRs upstream to get these fixes into web3.js beta.37 and release Truffle v5.0.0 on a fork of web3 in the meantime.
Creating this issue to serve to track the resolution of all of this.
Summary of issues:
keepAlive: true
for HTTP agents. The proposed web3 change is to allowkeepAlive
as an option innew Web3.providers.HttpProvider()
.PR: web3/web3.js#2105
bytes
values from being decoded for emptyoutputs
. The proposed solution is to loosen the validation check to what appears to be more correct.PR: web3/web3.js#2106
Thanks to @eggplantzzz and @CruzMolina, respectively, for getting to the bottom of these.
cc @nivida so you're aware.
The text was updated successfully, but these errors were encountered: