fix: expose accepted execution backend in heartbeat output - #502
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.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.
Heartbeat checks already read accepted execution reports, but their successful output does not identify the execution backend. This change exposes only the existing gateway/quantconnect enum (otherwise unknown), bound to the report timestamp, and retains the newest accepted report per required target. It does not read secrets or change report acceptance, health, notifications, or trading behavior.
Validation: 39 focused heartbeat and runtime-policy tests passed; Ruff and git diff --check passed. Tests cover invalid backend values without echoing them, rejected reports, and newest accepted report selection. Live backend readback remains to be verified after publication through the existing lifecycle workflow.