Repository navigation
chore(OMN-12667): bump zone-filter workflow ref - #1860
Merged
Merged
Conversation
|
Warning Review limit reached
More reviews will be available in 7 minutes and 59 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jun 4, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jun 4, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jun 4, 2026
5 tasks done
jonahgabriel
added a commit
that referenced
this pull request
Jul 5, 2026
…defect) The self-hosted CI runner image's bundled GitHub Actions node runtime (used by node-based actions, e.g. pyright) dlopens libatomic.so.1 at load time. Ubuntu 22.04 does not pull libatomic1 in transitively, so every node-based action fails with "node: libatomic.so.1: cannot open shared object file" — deterministic, not transient. Blocks omniclaude PR #1860 (OMN-13502) and any omniclaude PR that runs pyright. Add libatomic1 to the runner image apt install list, bump image_version 5->6 (real image content change), and regenerate the bound identity (docker/runners/runner-image.lock.json). The Dockerfile apt-list is not itself a binding input, so identity_digest only moves because image_version does; shared_env_digest is unchanged. Updates the OMN-12765 release-backmerge identity-pin test to the regenerated digest. Rebuild + fleet redeploy on .201 is a separate gated live-runtime step, out of scope here. Evidence-Source: OCC#TBD Evidence-Ticket: OMN-13946
jonahgabriel
added a commit
that referenced
this pull request
Jul 5, 2026
…defect) The self-hosted CI runner image's bundled GitHub Actions node runtime (used by node-based actions, e.g. pyright) dlopens libatomic.so.1 at load time. Ubuntu 22.04 does not pull libatomic1 in transitively, so every node-based action fails with "node: libatomic.so.1: cannot open shared object file" — deterministic, not transient. Blocks omniclaude PR #1860 (OMN-13502) and any omniclaude PR that runs pyright. Add libatomic1 to the runner image apt install list, bump image_version 5->6 (real image content change), and regenerate the bound identity (docker/runners/runner-image.lock.json). The Dockerfile apt-list is not itself a binding input, so identity_digest only moves because image_version does; shared_env_digest is unchanged. Updates the OMN-12765 release-backmerge identity-pin test to the regenerated digest. Rebuild + fleet redeploy on .201 is a separate gated live-runtime step, out of scope here. Evidence-Source: OCC#TBD Evidence-Ticket: OMN-13946
jonahgabriel
added a commit
that referenced
this pull request
Jul 8, 2026
…defect) The self-hosted CI runner image's bundled GitHub Actions node runtime (used by node-based actions, e.g. pyright) dlopens libatomic.so.1 at load time. Ubuntu 22.04 does not pull libatomic1 in transitively, so every node-based action fails with "node: libatomic.so.1: cannot open shared object file" — deterministic, not transient. Blocks omniclaude PR #1860 (OMN-13502) and any omniclaude PR that runs pyright. Add libatomic1 to the runner image apt install list, bump image_version 5->6 (real image content change), and regenerate the bound identity (docker/runners/runner-image.lock.json). The Dockerfile apt-list is not itself a binding input, so identity_digest only moves because image_version does; shared_env_digest is unchanged. Updates the OMN-12765 release-backmerge identity-pin test to the regenerated digest. Rebuild + fleet redeploy on .201 is a separate gated live-runtime step, out of scope here. Evidence-Source: OCC#TBD Evidence-Ticket: OMN-13946
jonahgabriel
added a commit
that referenced
this pull request
Jul 9, 2026
…defect) (#2207) * fix(OMN-13946): add libatomic1 to runner image (Pyright node runtime defect) The self-hosted CI runner image's bundled GitHub Actions node runtime (used by node-based actions, e.g. pyright) dlopens libatomic.so.1 at load time. Ubuntu 22.04 does not pull libatomic1 in transitively, so every node-based action fails with "node: libatomic.so.1: cannot open shared object file" — deterministic, not transient. Blocks omniclaude PR #1860 (OMN-13502) and any omniclaude PR that runs pyright. Add libatomic1 to the runner image apt install list, bump image_version 5->6 (real image content change), and regenerate the bound identity (docker/runners/runner-image.lock.json). The Dockerfile apt-list is not itself a binding input, so identity_digest only moves because image_version does; shared_env_digest is unchanged. Updates the OMN-12765 release-backmerge identity-pin test to the regenerated digest. Rebuild + fleet redeploy on .201 is a separate gated live-runtime step, out of scope here. Evidence-Source: OCC#TBD Evidence-Ticket: OMN-13946 * chore(OMN-13946): retrigger occ-preflight after PR body Evidence-Source update * chore(OMN-13946): retrigger required PR checks * ci(OMN-13946): harden uv sync validator gates * ci(OMN-13946): refresh kafka gates after runner install casualty
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.
Ticket: OMN-12667
Evidence-Source: e4897be094cc268ae6f0bedde58580cdda0e70ea
Evidence-Ticket: OMN-12667
Summary
.github/workflows/ci.ymltoa1e73fff25a05ccb37cbb92d9c91754c59d808c0.Verification
uv run python -c 'from pathlib import Path; import yaml; data=yaml.safe_load(Path(".github/workflows/ci.yml").read_text()); assert data["jobs"]["zone-filter"]["uses"].endswith("@a1e73fff25a05ccb37cbb92d9c91754c59d808c0"); print(data["jobs"]["zone-filter"]["uses"])'\n-grep -n 'zone-filter.yml@a1e73fff25a05ccb37cbb92d9c91754c59d808c0' .github/workflows/ci.yml\n- Central OCC evidence merged in evidence(OMN-12667): bind infra zone-filter bump receipts onex_change_control#2144 (e4897be094cc268ae6f0bedde58580cdda0e70ea)\n\nSupersedes: chore(deps): bump OmniNode-ai/omnibase_core/.github/workflows/zone-filter.yml from 296431f68a7431b9a98cd3661c6a2e05d1a18e45 to a1e73fff25a05ccb37cbb92d9c91754c59d808c0 #1853