nix-eval-jobs unknown settings warnings (fixed upstream) #1108
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lix-project/lix#1108
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
When running
nix-eval-jobswith a configuration withallowed-usersand/ortrusted-usersset to any value, it will spit out warnings:This is fixed (hacked around) by this PR upstream, but not in a release yet, and this is the upstream issue.
Not sure if that's the best way to fix this, of course.
It would be nice if this or some fix like this was applied to the lix version of nix-eval-jobs.
Steps To Reproduce
nix-eval-jobs(fromlixPackageSetsor fromlixmain).2> >(rg -v "unknown setting \'(allowed|trusted)-users" > /dev/null))Expected behavior
Ideally, valid settings would not print warnings.
nix --versionoutput@ma27 can you take a look and advise/port if this makes sense? Thanks!
@raito how dumb would it be to just add the settings globally? AFAIU this (i.e. config initialization) happens during
initNix();when using the C++ API, so not only n-e-j, but also every Hydra component is affected.