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 was archived by the owner on Mar 5, 2025. It is now read-only.
@nivida That's it, thank you. 🤦♂️ Looks like I copied https endpoint and changed to wss, missing the /ws.
Is it the correct behavior for web3.eth.subscribe to not log an error when the provider is responding with 404 errors? If the callback for web3.eth.subscribe isn't the place to catch the 404, where would be the correct place?
Thanks for opening this issue!
No this isn't the correct behavior. I will add the socket error handling here.
nivida
changed the title
@nivida That's it, thank you. 🤦♂️ Looks like I copied https endpoint and changed to wss, missing the /ws.
Improve error handling of subscriptions
Apr 25, 2019
@nivida That's it, thank you. 🤦♂️ Looks like I copied https endpoint and changed to wss, missing the
/ws
.Is it the correct behavior for
web3.eth.subscribe
to not log an error when the provider is responding with404
errors? If the callback forweb3.eth.subscribe
isn't the place to catch the404
, where would be the correct place?Originally posted by @carterbrett in #2706 (comment)
The text was updated successfully, but these errors were encountered: