fluencelabs / fluencelabs/aquavm
Collecting execution info
Open
Nobody has claimed this yet.
C-enhancement
C-feature
P-low
- Dominant language
- Rust
- Stars
- 154
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
It's necessary to collect some statistics and information of execution air script from a particle:
- how many instructions were handled
- how many hops are made
- how many instructions are to be handled
- if there any chance that execution will get back to this node
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
The issue names no files, tests, or entry points, so first map where AquaVM executes AIR and where execution state is represented. Define how each listed statistic is collected and exposed, then add coverage showing instruction counts, hop counts, remaining work, and whether execution may return to the node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100