-
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
Websocket closes immediately in < beta41, "too many arguments" err with beta41 #2327
Comments
Thanks for submitting this issue! Will check and fix it asap. |
I found that the node returns |
I think we already had this discussion here: #1217 (comment) This should be the solution for you. I will write it down on my check-list maybe I find a better solution. |
is not fixing the problem, neither in beta37 nor in beta41, clientOptions doesnt work either. I still get a 'Normal connection closure', event in beta37 and a undefined subscription in beta41 Also @nivida it would be nice if you close the issue AFTER you get confirmation that something is fixed. Because this bug is not fixed. |
@gnorbsl: My mistake was an incorrect request in the batch. Maybe the error output can be more clear. Incorrect request: Should be: |
Expected behavior
Connect to geth over websocket.
Actual behavior
instance=Geth/v1.9.0-unstable-7c60d0a6/linux-amd64/go1.11.5
on beta < 41 the websocket closes immediately after opening it, .on('end') reports a normal closure. Node doesn't report anything.
With beta 41 Node throws error
INFO [02-05|15:07:53.142] Served eth_subscribe conn= reqid=1 t=34.22µs err="too many arguments, want at most 1"
on latest geth stable
instance=Geth/v1.8.22-stable-7fa3509e/linux-amd64/go1.11.5
with beta 41 I get this error:Steps to reproduce the behavior
install latest geth stable
install latest web3js
try to establish websocket connection with
Error Logs
Versions
$ npm -v
6.7.0
$ node -v
v8.15.0
The text was updated successfully, but these errors were encountered: