-
Notifications
You must be signed in to change notification settings - Fork 73
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
_binary_to_variant
function crashing on some blocks
#2228
Comments
The upgrade to leap/libraries/chain/abi_serializer.cpp Line 374 in 02da283
|
Works. |
What non-default options do you have on your |
And running the chain as
normally, and with snapshot
Building the image with
|
Hi @heifner, did you get a chance to look into this? |
Sorry, no. Hopefully someone can take a look soon. I will say that we had no other reports of issues with |
If it helps debug, the trace API running on eos.greymass.com only uses the following configuration for the trace_api:
We don't use any other trace related configuration options. We haven't seen any issues like this before - but we also don't decode server side, we handle decoding on the client that's making the request. |
Hi @cshintov - if Aaron's response does not correct the issue, you can contact me via email at ted.cahall@eosnetwork.com and we can set up a call or chat to discuss other options. |
hi all, on behald of @cshintov @aaroncox yes, you're not deserializing using abi as we do on server side, so no issues when we tried that option, we're getting raw output @tedcahalleos I've tried to comment out eosio.token abi from the config file - then I'm able to get trace from the node (with using latest cdt 4.0.1 all these don't work with eosio.token abi enabled for the same error 357118176 thanks |
@tmeinlschmidt Please email me at ted.cahall@eosnetwork.com so we can discuss offline. We are done with this ticket in terms of helping diagnose without speaking to you offline. Happy to set up a call or zoom once you contact me. |
[3.2] TraceAPI: Correctly convert return value via ABI
[3.2 -> 4.0] TraceAPI: Correctly convert return value via ABI
[4.0 -> 5.0] TraceAPI: Correctly convert return value via ABI
[5.0 -> main] TraceAPI: Correctly convert return value via ABI
I'm running 6 mainnet archive nodes, today morning onwards on all of them, a few blocks are returning 500, internal server error!
The nodes are running v4.0.5.
I tried rewinding the node back using
But afterwards it complained about database version mismatch.
So I tried syncing from a recent snapshot snapshot-2024-02-08-04-eos-v6-0356339018.bin
Even then this block was returning the same error.
There are a few more blocks like this in the next 10k range!
Is this a network wide issue, or only for me, how to recover?
Only thing left to do is to upgrade to
v5.0.0
which I'm currently trying.The text was updated successfully, but these errors were encountered: