You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.
I didn't think this was supposed to be a thing, but it appears some versions of web3 will return a null value for transaction has on the .once('transactionHash') event handler.
* small logic adjustments to how weird transaction hash values are handled. Issues #3573#3574#3275
* prevent refetch when hash is pending, and integrate @nick's feedback
Added some instrumentation with #3589. This issue will get a unique error now and also dump the transaction to console for diagnostics. According to other reports on the interwebs, this can be caused by a gas prices being too low for the node to accept, and possibly other transaction errors.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugSomething isn't working as intendedgraphqlP2Small number of users are affected, major cosmetic issue
https://sentry.io/organizations/origin-protocol/issues/1247501267/events/848d565c124c49b7966b976ac9dcf85a/?project=1402589
I didn't think this was supposed to be a thing, but it appears some versions of web3 will return a
null
value for transaction has on the.once('transactionHash')
event handler.Ref #3275
The text was updated successfully, but these errors were encountered: