Repository navigation
Repair v17 registry binding and bound CI observer installation - #225
Merged
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
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.
The hosted v17 trial failed before provider configuration because the caller pinned a runtime with the manifest engine but an older contract registry. All caller and admission pins now select b075e50, which contains both. Actual provider-free resolver execution reproduces rejection at dd01 and resolves the exact v17 profile and limits at b075. Existing profile bytes, budgets, and the v14 default remain unchanged.
The installed-observer CI job also stalled during apt index updates for its entire 20-minute deadline. Installation now uses existing strace or at most two 60-second attempts under a three-minute step deadline. Missing strace still fails the check; the actual roundtrip test remains required.
Validation: 111 focused tests passed with one expected skip in author, root, and independent runs. Fake commands cover installed, retry-success, persistent failure, and successful apt without strace. Independent code and documentation reviews CLEAR; Ruff, YAML, shell syntax, and diff checks passed. No provider calls or target writes occurred during these checks. The failed hosted trial is retained as run 37674535411; provider configuration, analysis, and publication steps were skipped.