-
Notifications
You must be signed in to change notification settings - Fork 5k
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
RequestManager/SocketProvider never resolves Web3Deferred Promise when using IPC Provider #7323
Comments
The team will review this soon @fipso |
@fipso - which Ethereum node are you connecting to with IPC? Have you checked the IPC configuration options? There is an open PR to fix the broken link to the definition of the SocketConstructorOps type - here is an updated link in the meantime. |
Hello, the Node I am using is Nethermind. As the nethermind IPC socket is requiring a /n after each JSON object it receives I got a reverse proxy in front of it that adds a /n to each message and forwards it. I tested the reverse proxy with different nodes and client libraries so I can be sure the issue is probably not there. |
Thanks for reporting the issue @fipso, |
Hi @fipso,
I see that your function name is |
Closing this issue as could not replicate and it might be the case described here: #7323 (comment) However, if this issue persists, kindly re-open the issue the provide more information. (By the way, having trouble running Nethermind locally: NethermindEth/nethermind#7801) |
Steps to reproduce the behavior
I debugged my way to the SocketProvider's send function. For some reason, when I place a breakpoint at the end of the function
return deferredPromise;
line 494, wait for like 2 seconds, then i continue execution and suddenly it works and the promise resolves with the right number.Environment
Fedora 40, Node v20.17,
"web3": "^4.13.0",
"web3-providers-ipc": "^4.0.7"
The text was updated successfully, but these errors were encountered: