Conversation
The runtime exe embeds the product's driver+tfs closure; tebako#600's boundary synthesis (slice mounts below a declared point materialize their intermediate directories) rides that unit, so the catalog re-cuts on it. Contract unchanged (2).
v2.8.3's gnu legs died on the focal floor's curl (--retry-all-errors, 7.71+ flag on 7.68) — a partial release with no linux-gnu units. v2.8.4 re-runs the full pipeline with the fix and carries the private asset-descriptor fetch + bundle --also on top of the boundary synthesis.
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 12:59 — with 
GitHub Actions
Failure
GitHub Actions
Failure
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 12:59 — with
GitHub Actions
Failure
GitHub Actions
Failure
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 13:01 — with
GitHub Actions
Failure
GitHub Actions
Failure
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 13:01 — with
GitHub Actions
Failure
GitHub Actions
Failure
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 13:01 — with
GitHub Actions
Failure
GitHub Actions
Failure
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 13:01 — with
GitHub Actions
Failure
GitHub Actions
Failure
…idge The v2.8.4 link unit's driver embeds the spec 17 §2.3 trust bridge's OS-store enumeration (rustls-native-certs → security-framework objects): its kSec*/_Sec*/_CMS*/_Authorization* references resolve only against the system Security framework, and miniruby's link died on the undefined set (all four macos legs). Scoped to the v2 (rust_libdir) link. Also: the windows failure dump now names a non-starting miniruby's import table and runs it bare (the Error 127 class identifies itself).
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 13:57 — with
GitHub Actions
Error
GitHub Actions
Error
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 13:57 — with
GitHub Actions
Error
GitHub Actions
Error
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 13:57 — with
GitHub Actions
Error
GitHub Actions
Error
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 13:57 — with
GitHub Actions
Error
GitHub Actions
Error
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 13:57 — with
GitHub Actions
Error
GitHub Actions
Error
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 13:57 — with
GitHub Actions
Error
GitHub Actions
Error
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 13:58 — with
GitHub Actions
Failure
GitHub Actions
Failure
…s, ldd, PE headers, cmd-native spawn The exact-recipe re-run 127s with zero output even bare: the exe starts and exits 127 silently. Split the remaining causes: subsystem/entry corruption (objdump), DLL resolution (ldd), msys2 spawn translation (cmd /c ERRORLEVEL), ruby-level reachability (-e puts), AV locks (copy to /tmp).
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 14:52 — with
GitHub Actions
Error
GitHub Actions
Error
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 14:52 — with
GitHub Actions
Error
GitHub Actions
Error
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 14:53 — with
GitHub Actions
Error
GitHub Actions
Error
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 14:59 — with
GitHub Actions
Failure
GitHub Actions
Failure
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 14:59 — with
GitHub Actions
Failure
GitHub Actions
Failure
…n artifact The silent 127 reproduces bare, under cmd, and from a copy — the exe exits 127 before any stdio. The miniruby link's own output is lost (the -j4 output is discarded by the serial retry), so relink it in the dump with V=1, and upload the exe + Makefile for offline dissection.
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 15:19 — with
GitHub Actions
Failure
GitHub Actions
Failure
ronaldtse
had a problem deploying
to
windows-signing
September 15, 2026 15:19 — with
GitHub Actions
Failure
GitHub Actions
Failure
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
2 participants
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.
What
Pin the consumed link unit at tebako v2.8.4 and cut runtime 0.16.24.
contract.yml:link_unit_release: "v2.3.0"→"v2.8.4". Contract version unchanged (2) — the change is behavioral, inside the unit's tfs engine.VERSION: 0.16.23 → 0.16.24. Full-catalog re-cut: the runtime exe embeds the unit, so every (version × triplet) republishes.Why
v2.8.4 (tebako#600) makes the unit's tfs engine synthesize mount-boundary directories: a slice mounted below a point the runtime never declared (
/flavors.d/<name>) used to answer ENOENT for the intermediate components, so the payload interpreter's realpath/glob walk across the boundary failed (Gem.paths=died withErrno::ENOENT @ realpath_rec). The ancestors now materialize as directories at mount time.This is the runtime-side half of the extension-slice flow: without it, a toolkit slice mounted under
/flavors.d/cannot be seen by the base payload's gem path setup.Pin mechanics
The legs download
link-unit-2.8.4-<triplet>.tar.gzfrom the published v2.8.4 release (all five platforms present, verified). A platform with no published unit would fall back to source build — a miss is never an error — but v2.8.4 is complete, so all legs hit the pin.