Joystream / Joystream/joystream
Any failed extrinsics prevents Polkadot apps to read the block contents
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
- Try executing sudo.setKey()
- Sign and submit
- Observe green status (as if transaction went fine!)
- Switch to explorer, try to view the block
- Observe an error
Unable to retrieve the specified block details. Unable to decode storage system.events:: createType(Vec<EventRecord>):: Vec<EventRecord>:: Decoded input doesn't match input, received 0x0c00000000000000482d7c0900000000020000000100000000000000000000000000020000000200000000010310000000000000000000000000 (58 bytes), created 0x0c00000000000000482d7c0900000000020000000100000000000000000000000000020000000200000000010310000000000000000000000000000000 (61 bytes)
The consequence of this new regression is that I as the user cannot see the error codes coming from the pallet anymore. Tx is shown as green, but the block contents cannot be decoded for troubleshooting anymore!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by submitting sudo.setKey(), then switch to the explorer and inspect the failed block's event decoding. Determine why a failed extrinsic prevents the block contents from being decoded; done means the block is readable and the pallet error codes remain visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100