Treat no-action monthly Firstrade runs as complete#74
Merged
Conversation
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
NO_ACTIONmonthly run state as a completed idempotency state.NO_ACTIONmonthly state skips later live runs in the same period.Why
Monthly snapshot strategies can legitimately complete with no orders. That result should stop later scheduled invocations from re-evaluating as if the month were unfinished.
Validation
PYTHONPATH=.:/home/ubuntu/Projects/QuantPlatformKit/src:/home/ubuntu/Projects/UsEquityStrategies/src /tmp/qsl-pytest-venv/bin/python -m pytest -q tests/test_rebalance_service.py::test_run_strategy_cycle_skips_duplicate_live_monthly_run tests/test_rebalance_service.py::test_run_strategy_cycle_skips_duplicate_live_monthly_no_action