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
Got response from unknown request #566
Comments
I can see in
And when I decode the raw bytes that I received I get what I was subscribed to:
It seems the same as #563 but in my case I'm using Infura. How could I bypass this limitation? Which eth node provider should I use to get this running? |
Still digging trying to understand why the websocket response fails to be decoded whereas the http works. Received http: {
"jsonrpc": "2.0",
"id": 93,
"result": [
{
"address": "0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640",
"blockHash": "0x88cd879b0d64a1a182148424e033498c2fef0903133dca66364fdf5fa41202b8",
"blockNumber": "0xcef012",
"data": "0x0000000000000000000000000000000000000000000000000000000242760b91ffffffffffffffffffffffffffffffffffffffffffffffffe1f87f7a58f76dfd0000000000000000000000000000000000003a579793d13959af617c84b3aaa400000000000000000000000000000000000000000000000109efec8446be0a78000000000000000000000000000000000000000000000000000000000002eeef",
"logIndex": "0x20",
"removed": false,
"topics": [
"0xc42079f94a6350d7e6235f29174924f928cc2ac818eb64fed8004e115fbcca67",
"0x000000000000000000000000e592427a0aece92de3edee1f18e0157c05861564",
"0x000000000000000000000000e592427a0aece92de3edee1f18e0157c05861564"
],
"transactionHash": "0xca67ee912802c0eb4fadfa98cdde71915c821e43f6ce11a98e2a33e1d3524afe",
"transactionIndex": "0x11"
}
]
} Websocket {
"JSONRPC": "2.0",
"method": "eth_subscription",
"params": {
"subscription": "0x10ff0e12f0313a0de8d542b1ae656ac614d451f456e2",
"result": {
"removed": false,
"logIndex": "0x156",
"transactionIndex": "0xe4",
"transactionHash": "0x901a47aa4f7dcc6f9f390171d40979856f0ea55a4e65455a824dc984cb237bf4",
"blockHash": "0xfeb0a0f446350eb6205c7a0f72168a108b9a953135cdabdca4e676c05362fdff",
"blockNumber": "0xcedd7b",
"address": "0x4e68ccd3e89f51c3074ca5072bbac773960dfa36",
"data": "0xffffffffffffffffffffffffffffffffffffffffffffffffdfcd05c3906437360000000000000000000000000000000000000000000000000000000272a39ffe0000000000000000000000000000000000000000000467a87e34429148e9ee3e000000000000000000000000000000000000000000000000912ef544f1c55642fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffd115d",
"topics": [
"0xc42079f94a6350d7e6235f29174924f928cc2ac818eb64fed8004e115fbcca67",
"0x000000000000000000000000e592427a0aece92de3edee1f18e0157c05861564",
"0x000000000000000000000000e592427a0aece92de3edee1f18e0157c05861564"
]
}
}
} |
Okay.. it turns out it was the capital case on I've created a PR on the jsonrpc library paritytech/jsonrpc#649 |
I'm also getting this warning while using ganache with instamine support. What's worse, the application hangs after this warning. To reproduce, run ganache as
And run the following code as
Then the log is:
and the application just hangs indefinitely. |
I managed to debug the issue. With ganache v7.0.3 (@ganache/cli: 0.1.4, @ganache/core: 0.1.4), the JSON-RPC respose is received as follows:
Note that the case of This means that, if the response fails to be parsed due to messages which do not conform to the JSON-RPC specification, we can't obtain the subscription id and pass any kind of message through the channel and the application will freeze indefinitely. This is unacceptable behavior. IMO, as long as the message request contains @tomusdrw you were the one to introduce strict parsing in I also think that assuming rust-web3/src/transports/ws.rs Line 295 in 0a32ab5
|
I implemented a workaround in #639. |
Hi, I'm trying to subscribe to events in a contract:
And everytime an event happens (checking on etherscan) I receive a response from unknown request
The same is happening when I try to run the examples subscribing to new heads.
I know my node connection is working because I can fetch past events and I receive the correct data
Any idea of what could be happening?
Thanks.
The text was updated successfully, but these errors were encountered: