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
When doing a call of getBlock with encoding set to jsonParsed for, for example, block 258768009, application crashes with the following trace:
thread '<unnamed>' panicked at src/lib.rs:62:60:
called `Result::unwrap()` on an `Err` value: short buffer: required 32 bytes, but only 4 bytes available
stack backtrace:
0: rust_begin_unwind
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:647:5
1: core::panicking::panic_fmt
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panicking.rs:72:14
2: core::result::unwrap_failed
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/result.rs:1649:5
3: parse_instruction
4: _cgo_3af86e38bd62_Cfunc_parse_instruction
at /tmp/go-build/cgo-gcc-prolog:67:11
5: runtime.asmcgocall
at /usr/local/go/src/runtime/asm_amd64.s:918
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
fatal runtime error: failed to initiate panic, error 5
SIGABRT: abort
PC=0x78acfb6969fc m=20 sigcode=18446744073709551610
signal arrived during cgo execution
After adding some more extra logs, it seems it crashes when trying to decode ExtendLookupTable instruction.
Due to the extended logs, we can get for the instruction which fails the following confusing line:
[rust] static_account_keys_len: 196
however, it has only four accounts required for this operation. Here is unparsed instruction:
The transaction signature from that block is 61KrK26PQohM8Qt1GR6WBRUXkLoWvFhUSnm3Q14EEMMHPsAo4iTrkx8EwZt2y7tQXVsgHyMmjzJiMncTjfE85LMa.
This is not the only case, sometimes it crashes on another blocks, this is only as an example. Possibly, for some instructions layout is read not correctly.
The text was updated successfully, but these errors were encountered:
Problem
When doing a call of
getBlock
with encoding set tojsonParsed
for, for example, block 258768009, application crashes with the following trace:After adding some more extra logs, it seems it crashes when trying to decode
ExtendLookupTable
instruction.Due to the extended logs, we can get for the instruction which fails the following confusing line:
however, it has only four accounts required for this operation. Here is unparsed instruction:
The transaction signature from that block is
61KrK26PQohM8Qt1GR6WBRUXkLoWvFhUSnm3Q14EEMMHPsAo4iTrkx8EwZt2y7tQXVsgHyMmjzJiMncTjfE85LMa
.This is not the only case, sometimes it crashes on another blocks, this is only as an example. Possibly, for some instructions layout is read not correctly.
The text was updated successfully, but these errors were encountered: