Repository navigation
Fetch fractal fixture through shallow Git - #129
Draft
schickling-assistant wants to merge 1 commit into
Draft
schickling-assistant wants to merge 1 commit into
schickling-assistant wants to merge 1 commit into
Conversation
Contributor
Author
|
CI Manager (agent/dotfiles/ci-manager) source review of #129 at 4497c2f: GO.
Posted on behalf of @schickling
|
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.
Problem
FPL reports that since approximately 21:37Z GitHub's api.github.com/repos/compoundingtech/fractal/tarball/ endpoint returns HTTP 504, while tarball/main and codeload still return 200. Fractal's unusually large public evidence-ref set is a suspected cause, not an established root cause. The current github: fixture input depends on that failing commit-tarball transport. This PR changes transport only; it does not repin fixture content or relax the oracle guard.
Change
Use the requested non-flake source:
Regenerate only the fractal-fixture lock node. Both locked and original are now type=git with shallow=true. Nix records locked.ref=refs/heads/main alongside the unchanged immutable locked.rev; the full revision remains the authority. flake=false is unchanged. Add a changelog note; no scripts, tests, other input pins or runtime policy are changed.
Source identity
Old github input narHash:
New shallow-Git input narHash:
They are equal. lastModified=1794333982 and rev=787e8ed592dff34d2bdc2a2b0b584482da567e7f are also unchanged. The source tree bytes/modes are preserved; no hand-written NAR hash or lock content was used.
Verification
Other inputs and downstream precedent
No other root or resolved lock input fetches compoundingtech/fractal by SHA. python-oracle still fetches compoundingtech/mergemaster/cff667cd (v0.6.0), and python-oracle-parity still fetches compoundingtech/mergemaster/1392a516 (v0.5.0); neither fetches Fractal and neither changes here. effect-utils and its toolchain inputs likewise do not introduce another resolved Fractal node.
Searched schickling/dotfiles open PRs for shallow, shallow in:title, and fractal in:title. No matching shallow-transport PR was found in those searches, so no unobserved Deps Manager diff is claimed. This implements the exact git+https/shallow=1 pattern requested by FPL/Main; dotfiles' existing follows-smalltalk relationship is not modified here.
NOT RUN
Nix builds/flake checks, cargo/Rust compilation or tests, full copied-script suite, workflow-generation tests, hosted exact-head CI, live reproduction/root-cause diagnosis of the reported tarball 504, dotfiles lock changes, deployment/restarts, push, PR creation or release publication. Existing guard source is unchanged; both requested Python entrypoints passed before the signed commit.
Posted on behalf of @schickling
agent_identitysessionagent_personaagent_supervisoragent_toolagent_tool_versionagent_runtimeagent_modelworktree