Repository navigation
Report a CLI that cannot start instead of asking for an update - #23
Merged
vladimir-tikhonov-nutrient merged 1 commit intoSep 28, 2026
Merged
Conversation
The nutrient entry point probed `auth --help` with its errors discarded and reported any failure as a missing-account-commands update problem. On Linux hosts without ICU, the .NET runtime aborts on that probe, so users were told to connect to the internet when the fix was installing a system library. Crashes (exit status 126 or higher) now show the binary's own first error lines without managed stack frames, plus the ICU package to install when the error names ICU. A binary that runs but predates account commands keeps the existing message. On Linux, a new install also probes a command that starts the runtime and warns once; the install still completes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
vladimir-tikhonov-nutrient
marked this pull request as ready for review
September 28, 2026 10:52
vladimir-tikhonov-nutrient
deleted the
vtikhonov/cli-start-failure-reporting
branch
September 28, 2026 10:53
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
On Linux hosts without the ICU libraries (stock
ubuntu:24.04and most slim container images), everynutrientcommand failed with:The binary wasn't outdated. The wrapper probes
auth --helpwith its errors discarded, and the .NET runtime aborts on that probe (exit 134) because it can't load ICU. Conversions crashed with a raw stack trace, and the install check never noticed because it runs only--version, which doesn't start the runtime.The underlying crash is in the native build (ICU is linked statically but not used by the runtime) and needs a GdPicture fix. This PR only makes the failure understandable.
Change
--versionsmoke test, the wrapper probesauth --helponce and prints the same diagnosis if the runtime can't start. The install still completes, so--version,--help, and--licensekeep working.apt-get install libicu-dev,apk add icu-libs, ordnf install libicu.The install logic stays byte-identical across the three entry points.
Verification
npm test: 10 of 10 pass, including two new cases, a cached binary that crashes on the probe and a freshly installed one that does.npm run checkandshellcheck -s shon all scripts: clean.sedfilter was checked on BSDsed(macOS) and GNUsed.ubuntu:24.04without ICU,nutrient --versionnow prints:🤖 Generated with Claude Code