tests/functional/common: check for UTF-8 support should be silenced, as not to create misleading stderr output #1056
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
awaiting
author
awaiting
contributors
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
Feature/S3
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lix-project/lix#1056
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the bug
Right now, if UTF-8 characters aren't supported in the shell/filesystem (e.g. due to locale issues), the check to avoid them currently splats an extraneous error message to
stderr.The relevant code is here:
https://git.lix.systems/lix-project/lix/src/branch/main/tests/functional/common/vars-and-functions.sh.in#L151
This should be tweaked to be silent, as there's not an actual error, here; and it appearing far above the actual error makes it seem like the thing to focus on.
Steps To Reproduce
Expected behavior
Our output should make it very clear where the error is.
Actual behavior
We throw a nice red herring, which in issues like #1042 has been confused for the actual error message.
In that issue:
nix --versionoutputfunctional-nix-shell-basic#1042