fix: harden runtime scheduling and notifications - #361
Conversation
Co-Authored-By: Codex <noreply@openai.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 55e730dbed
ℹ️ 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".
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7fcc9d81a8
ℹ️ 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".
| ( | ||
| f"{alias}-scheduler", | ||
| f"{alias}-probe-scheduler", | ||
| f"{alias}-precheck-scheduler", | ||
| ) |
There was a problem hiding this comment.
When the runtime guard derives its default scheduler pattern, this exact-name whitelist omits the ${cloud_run_service%-service}-warmup-scheduler job created and managed in .github/workflows/sync-cloud-run-env.yml. Consequently, a warmup authentication or dispatch failure that never reaches Cloud Run is filtered out before failure evaluation, allowing the guard to report OK when all other logs are clean; include the warmup job name for each service alias.
Useful? React with 👍 / 👎.
1 participant
Summary
Validation