graphprotocol / graphprotocol/graph-node
Fix/remove _padding fields in NEAR Rust/ASc conversion types
Open
Nobody has claimed this yet.
chains/near
Stale
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Currently we have a memory alignment issue in the runtime ABI implementation for AssemblyScript that didn't happen until we integrated with NEAR.
That's because the size and alignment of Ethereum types never revealed this weak point.
- Create tests for the current padding issues
- Solve the problem
Contributor guide
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 locating the runtime ABI implementation for AssemblyScript and the conversion types containing _padding fields. Reproduce the current memory-alignment problems with tests, then verify that the padding issue is resolved by running those tests.
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