Conversation
…librì, not colibri The behavioral check unpacks the archive and asserts 'coli info' output contains "colibri" — but the banner spells the project name "colibrì", with U+00EC, and no plain-ASCII "colibri" appears anywhere in the output. Every other assertion passed (engine found, ready): the second v1.1.0 tag build died purely on the accent. grep for the ASCII prefix "colibr". Reproduced and verified locally by simulating the full package+verify step (tar, clean-dir extract, coli info): old grep FAIL, new grep PASS. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
release verify: grep for "colibr" — the banner's accented "colibrì" failed the ASCII match
…ase title
The launcher printed the name with an accent ('colibri' with a grave i) while
the binary, the package, the commands and the archives are all plain ASCII
'colibri'. That inconsistency is what broke the v1.1.0 tag build: the release
verify step greps the 'coli info' output for 'colibri' and the accented banner
never contained it.
Fix the name, not the check: the banner, --version, the argparse description
and the section headers now print 'colibri', and the release verify keeps its
exact 'colibri' match (reverting the looser prefix grep from #516). The GitHub
Release title is ASCII too, matching the archives it ships.
Verified by replaying the CI package+verify sequence locally (tar, clean-dir
extract, coli info): banner reads 'colibri v1.1.0', exact grep PASS.
test-python green (135).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
name: the program is plain-ASCII "colibri" — banner, --version, release title (unblocks the v1.1.0 tag build)
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
1 participant
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.
Everything needed for the
v1.1.0tag to build and publish. Three attempts, three distinct defects in the tag-only code path, all now fixed and each verified:make glm→ls glm). Only a tag push runs this file, which is why every CI stayed green while the tag build died.colibri; the release verify greps forcolibriand never found it. The name is fixed (banner,--version, Release title), and the verify keeps its exact match.COLI_TEMP(fixes [Bug]: TEMP env var conflicts with ROCm on AMD GPUs causing SIGSEGV #509 —$TEMPis the ROCm/Windows temp-directory, so--temp 0.6crashed HIP init, and on native Windows every run was silently greedy).colibri.exeready to run; the obsolete "rename it to glm.exe" step is gone from README and quickstart.The full CI package+verify sequence (tar → clean-dir extract →
coli info→ assertions) was replayed locally on the final state and passes.After merge: re-point the
v1.1.0tag at the new main head.🤖 Generated with Claude Code