Create Visual Workflow Debugger for Failed Tasks#626
Open
Godfrey-Delight wants to merge 1 commit into
Open
Conversation
Built a cross-layer debugging interface that instruments every gate and operation in the execution pipeline with step-level tracing. The Soroban contract now emits 15 distinct ExecutionStep events (Passed/Failed/Skipped) during execute_internal(), persists the full trace on-chain via ExecutionTrace storage, and exposes a get_execution_trace() query. The keeper captures trace data after successful execution and propagates it through the result pipeline. The frontend renders a color-coded timeline (ExecutionTraceViewer) that highlights exactly which condition failed, with error detail expansion and a failure summary banner. Closed SoroLabs#422
|
@Godfrey-Delight Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Built a cross-layer debugging interface that instruments every gate and operation in the execution pipeline with step-level tracing. The Soroban contract now emits 15 distinct ExecutionStep events (Passed/Failed/Skipped) during execute_internal(), persists the full trace on-chain via ExecutionTrace storage, and exposes a get_execution_trace() query. The keeper captures trace data after successful execution and propagates it through the result pipeline. The frontend renders a color-coded timeline (ExecutionTraceViewer) that highlights exactly which condition failed, with error detail expansion and a failure summary banner.
Related Issue
Closed #422
Type of Change
Changes Made
Added 15-step execution trace pipeline with on-chain storage, event emission per gate, and get_execution_trace() query. 140 tests pass.
Keeper captures trace after execution; frontend renders a color-coded ExecutionTraceViewer timeline highlighting the exact failed condition.
Validation
cargo fmt --all(ifcontractchanged)npm run lintinfrontend(iffrontendchanged)Screenshots (if UI changes)
Checklist