Skip to content

The stdio gateway finishes connecting before it answers

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Aug 12:24
· 11 commits to main since this release
v1.20.0
19e83c7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Bug fixes

  • hypergated --stdio could answer a request before it had finished attaching. It connected its stdio channel first and only then looked up the upstream tool list and reported which daemon it had attached to. A harness that acted on the first response and exited immediately could miss that report entirely.

    Everything that can fail, and everything worth logging, now happens before the stdio channel starts serving.

  • A failure at exactly the wrong moment could leave two servers on one channel. If the tool lookup failed after the stdio channel was already connected, the proxy reported that it had not attached, and the fallback path connected a second stdio server to the same input. Both would have been reading the same stream. The reordering above makes that unreachable, since every failure is now handled before anything is connected.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.20.0.tgz hypergated-1.20.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

Assets 35
Loading