paritytech / paritytech/revive
Detect problematic blob size at link time
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- Rust
- Stars
- 102
- Forks
- 26
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 6
Description
Emit a compiler warning (or error) if we detect the final blob size to exceed the pallets limits.
Tasks
- Add a command line flag to provide the memory limit (different chains can exhibit different limits), and assume AH as default
- Helper to calculate the maximum linked blob size given the static memory buffer and the the pallet limits
- Check it after linting and emit a warning if over the threshold
- By default it should error out but we want to have a flag to ignore it
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 reading the pallet limits in substrate/frame/revive/src/limits.rs, then locate the compiler's linking and post-lint entry points. Trace how command-line flags are defined and how the final blob size is available after linting. Done means configurable memory limits and ignore behavior are supported, with an error or warning when the calculated size exceeds the threshold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100