-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Execution tracing: GraphQL query to get storage inputs for past blocks #2491
Open
Dentosal
wants to merge
29
commits into
master
Choose a base branch
from
dento/execution-trace
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Dentosal
added
enhancement
New feature or request
fuel-block-executor
wasm
WASM-based block execution
labels
Dec 11, 2024
8 tasks
Dentosal
force-pushed
the
dento/execution-trace
branch
from
December 19, 2024 15:18
8d80d7b
to
3ba2bc7
Compare
4 tasks
Dentosal
changed the title
Execution tracing for past blocks
Execution tracing: add GraphQL endpoint to get storage inputs for past blocks
Jan 15, 2025
Dentosal
changed the title
Execution tracing: add GraphQL endpoint to get storage inputs for past blocks
Execution tracing: GraphQL query to get storage inputs for past blocks
Jan 15, 2025
Dentosal
added a commit
to FuelLabs/fuels-rs
that referenced
this pull request
Jan 17, 2025
- Related to #1432 # Release notes In this release, we: - Changed `ABIDecoder` methods to take `std::io::Read` instead of `&[u8]`, allowing it to be used in a streaming manner. # Summary `ABIDecoder` methods take `bytes: impl std::io::Read` instead of `bytes: &[u8]`. This allows decoding abi types without having to know the size in advance. This is particularly useful when reading them directly from VM memory, which will be used by the indexer after FuelLabs/fuel-core#2491 is done. # Breaking Changes `ABIDecoder` methods take `bytes: impl std::io::Read` instead of `bytes: &[u8]`. Callers using arrays or `Vec` must change the argument from `&value` to `value.as_slice()`. # Checklist - [x] All **changes** are **covered** by **tests** (or not applicable) - [x] All **changes** are **documented** (or not applicable) - [x] I **reviewed** the **entire PR** myself (preferably, on GH UI) - [x] I **described** all **Breaking Changes** (or there's none) --------- Co-authored-by: hal3e <[email protected]> Co-authored-by: Ahmed Sagdati <[email protected]> Co-authored-by: segfault-magnet <[email protected]>
Dentosal
requested review from
xgreenx,
MitchTurner,
netrome and
acerone85
as code owners
January 24, 2025 23:43
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
To support local debugging and execution tracing, we need to add an API that returns the state that VM needs to execute transactions. This is done by recording all database accesses during tx validation, called storage read replay (bikeshedding in progress). This data is then exposed as-is through GraphQL. The API is non-trivial to consume, but a seperate client is proviced, see https://github.com/FuelLabs/execution-trace
The implementation exposes database table names and representations directly. Maintaining backwards compatibility with this could turn out to be quite hard.
Follow-ups:
Example query:
TODO
--debug
flagOpen questions:
--debug
flag to enabled this, as opposed to super-high query cost or a separate flag to enable?Checklist
Before requesting review
After merging, notify other teams
See the VM PR FuelLabs/fuel-vm#881.