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
To reproduce simply create a Nethermind <-> Nimbus node where on nimbus webSockets will be enabled: --web3-url=ws://execution:8551/
Start the node and at Nethermind logs at the very first RPC received from Nimbus you should get this exception:
2024-05-15 10:07:00.9452|ERROR|JsonRpc.JsonRpcProcessor|76|Error during parsing/validation. System.Text.Json.JsonReaderException: The input does not contain any JSON tokens. Expected the input to start with a valid JSON token, when isFinalBlock is true. LineNumber: 1 | BytePositionInLine: 0.
at System.Text.Json.ThrowHelper.ThrowJsonReaderException(Utf8JsonReader& json, ExceptionResource resource, Byte nextByte, ReadOnlySpan`1 bytes)
at System.Text.Json.JsonDocument.TryParseValue(Utf8JsonReader& reader, JsonDocument& document, Boolean shouldThrow, Boolean useArrayPools)
at Nethermind.JsonRpc.JsonRpcProcessor.TryParseJson(ReadOnlySequence`1& buffer, JsonDocument& jsonDocument) in /_/src/Nethermind/Nethermind.JsonRpc/JsonRpcProcessor.cs:line 369
at Nethermind.JsonRpc.JsonRpcProcessor.ProcessAsync(PipeReader reader, JsonRpcContext context)+MoveNext() in /_/src/Nethermind/Nethermind.JsonRpc/JsonRpcProcessor.cs:line 157
2024-05-15 10:07:00.9452|DEBUG|JsonRpc.JsonRpcService|76|Sending error response, method: none, id: , errorType: -32700, message: Incorrect message, errorData:
To reproduce simply create a Nethermind <-> Nimbus node where on nimbus webSockets will be enabled:
--web3-url=ws://execution:8551/
Start the node and at Nethermind logs at the very first RPC received from Nimbus you should get this exception:
Looking at RPC Recorder output there is:
Which shows that RPC works well but for every request two responses are being generated (one valid and one invalid).
Node works fine but producing a lot of exceptions.
The text was updated successfully, but these errors were encountered: