Repository navigation
refactor(committor): unify transaction execution #1769
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
Draft
snawaz
wants to merge
1
commit into
refactor/committor-remove-legacy-tasks
from
refactor/committor-unify-execution
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Document that
finalize_signaturecan equalcommit_signature.The new rustdoc says
finalize_signatureis the "Signature of the subsequent actions or undelegations." This is not always true. InTransactionExecutor::execute_current, a follow-up transaction can fail withActionsError. If removing its actions leavescurrent.optimized_tasksempty, the executor returnsOk(commit_signature). No follow-up transaction is sent.ExecutionOutput::TwoStagethen holds the same signature in both fields.persist_resultstores that value asfinalize_stage_signature. The integration testtest_two_stage_action_failure_keeps_combined_commitasserts this behavior. Readers of the persisted signatures need this case documented.📝 Proposed doc fix
TwoStage { /// Signature of the transaction containing the combined commits. commit_signature: Signature, - /// Signature of the subsequent actions or undelegations. + /// Signature of the subsequent actions or undelegations. + /// Equals `commit_signature` when every follow-up action failed and + /// no follow-up transaction was sent. finalize_signature: Signature, },As per path instructions: "Check docs and rustdoc for factual consistency with the code. Flag only real mismatches, broken examples, stale comments, or important omissions."
📝 Committable suggestion
🤖 Prompt for AI Agents
Source: Path instructions