Harden scheduler switch guards#149
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a706fe3a1b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| continue | ||
| candidates.append(service_name) | ||
| if service_name.endswith("-service"): | ||
| candidates.append(service_name.removesuffix("-service")) |
There was a problem hiding this comment.
Anchor derived scheduler aliases
When RUNTIME_GUARD_SCHEDULER_JOB_PATTERN is unset, adding the stripped alias as a bare regex alternative makes the runtime guard match sibling jobs that only share the prefix. For example, with configured service longbridge-quant-hk-service, the generated longbridge\-quant\-hk alternative also matches longbridge-quant-hk-verify-service-scheduler, so a failure in that separate scheduler job would be reported against this guard run. Please constrain the generated alternatives to the intended scheduler job names or boundaries.
Useful? React with 👍 / 👎.
Summary
Tests