haskell-wasm CI: add archive.org fallback for the ghc-wasm-meta input - #1304
Merged
Conversation
palas
requested review from
a team,
CarlosLopezDeLara,
Jimbo4350,
carbolymer,
disassembler and
erikd
as code owners
August 19, 2026 20:51
Contributor
There was a problem hiding this comment.
Pull request overview
Improves the haskell-wasm GitHub Actions workflow resilience by proactively prefetching the ghc-wasm-meta flake input and falling back to an archive.org mirror when gitlab.haskell.org is unavailable, with integrity enforced via narHash.
Changes:
- Add a prefetch step that fetches
ghc-wasm-metafromgitlab.haskell.org, with an archive.org fallback on failure. - Add a changelog fragment documenting the CI resilience improvement for
cardano-wasm.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/haskell-wasm.yml | Adds a nix flake prefetch step with gitlab→archive.org fallback for ghc-wasm-meta. |
| .changes/20260819_210000_cardano-wasm_palas_wasm_ci_ghc_wasm_meta_mirror_fallback.yml | Records the workflow resilience change as a maintenance entry for cardano-wasm. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
gitlab.haskell.org is the only non-GitHub host among our flake inputs, and an outage breaks this workflow at `nix develop` time. Pre-fetch the ghc-wasm-meta input before the first nix invocation; if gitlab.haskell.org does not respond, fetch a byte-identical mirror of the pinned tarball from archive.org instead. The input's narHash from flake.lock is enforced on both sources, so the fallback cannot alter the build inputs; once the content is in the local store, the later nix invocations resolve the locked input without contacting gitlab. Mirror: https://archive.org/details/ghc-wasm-meta-c662c34d608dc9d2ff599b007f2e3c46138efaab If the input is re-pinned, upload the new GitLab archive tarball to an archive.org item named ghc-wasm-meta-<rev> (keeping GitLab's file name) to keep the fallback working; the step fails with instructions otherwise
palas
force-pushed
the
wasm-ci-gitlab-fallback
branch
from
August 19, 2026 20:59
a39193b to
51b091c
Compare
Jimbo4350
approved these changes
Aug 20, 2026
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.
Context
gitlab.haskell.org is the only non-GitHub host among our flake inputs, and an outage breaks this workflow at
nix developtime. Pre-fetch the ghc-wasm-meta input before the first nix invocation; if gitlab.haskell.org does not respond, fetch a byte-identical mirror of the pinned tarball from archive.org instead. The input's narHash from flake.lock is enforced on both sources, so the fallback cannot alter the build inputs; once the content is in the local store, the later nix invocations resolve the locked input without contacting gitlab.Mirror: https://archive.org/details/ghc-wasm-meta-c662c34d608dc9d2ff599b007f2e3c46138efaab If the input is re-pinned, upload the new GitLab archive tarball to an archive.org item named ghc-wasm-meta- (keeping GitLab's file name) to keep the fallback working; the step fails with instructions otherwise.
How to trust this PR
If the CI is still working this clearly did no harm. It should work the same as before except for when gitlab is down.
Checklist
.changes/