fix(receipts): IBKR no_signal / no_rebalance outcomes - #517
Merged
Merged
Conversation
Pin QPK for the expanded receipt outcomes, map only explicit no_op reasons, and default blank no-target cycles to no_signal without rewriting other no-ops. Co-authored-by: Cursor <cursoragent@cursor.com>
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
f982aea(#609) sono_signal/no_rebalancereceipts validate.no_signal,target_diff_below_threshold/no_rebalance) when the cycle would otherwise beno_action; keep ambiguous no-ops and dry-run asno_actionfor digest compatibility.no_op_reason=no_signalso the producer has a clear reason without rewriting window/guard reasons.Test plan
uv run --with pytest python -m pytest tests/test_execution_receipt_adapter.py -q(16 passed)Made with Cursor