paritytech / paritytech/frame-decode
ElectionProviderMultiPhase.SignedSubmissionsMap fails to decode on block 6348646
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 8
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Not enough data to fill buffer.
Using https://github.com/jsdw/polkadot-historic-decoding-example with the following command hits this:
cargo run --release -- decode-storage-items --types ../frame-decode/types/polkadot_types.yaml --spec-versions polkadot_old_spec_changes.json --connections 3 --starting-number 754 --starting-entry ElectionProviderMultiPhase.SignedSubmissionsMap
We can run the JS version of the command (ie in the /js folder in that repo) with:
./index.js decode-storage-items --block 6348646 --entry ElectionProviderMultiPhase.SignedSubmissionsMap
Curiously, offhand it looks like both get to the same decode result, and perhaps both run out of bytes and don't finish in the same way.
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
Start by reproducing the cargo run command against block 6348646 and the ElectionProviderMultiPhase.SignedSubmissionsMap entry, then compare its result with the JS command in the linked polkadot-historic-decoding-example repository. Trace where decoding runs out of bytes; done means the affected storage entry decodes consistently without the buffer error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100