-
Notifications
You must be signed in to change notification settings - Fork 17
feat: add env_logger #32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
olebedev
wants to merge
2
commits into
xzfc:master
Choose a base branch
from
olebedev:oleg/add-logger
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cached-nix-shell --version
should not hide its version by default as it would confuse the user.Also, since the original
nix-shell --version
prints its version to stdout (not stderr), CNS should too.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. I think hiding/swallowing something, version for example or any other useful information is not great, 100%.
However, the intention of the PR is to hide everything that confuse tooling/scripting around automatic nix/nix-shell invocations, not humans. So I would like to tap on this one a bit more if you don't mind :)
In particular, printing anything extra into
stdout
(notstderr
) can have consequences like some tooling can fail due to an unexpected output, like three lines instead of one, like in this example. So the output is unrecognizable by tools if we replace vanillanix-shell
with the cached one.Another thing that worries me is that the output for
nix-store --version
andnix-shell --version
should be different in case if we decide to print it, right? Becausenix-store
has nothing to do withcached-nix-shell
. So we kind of introduce a divergence that we would rather avoid.What do you mean, a user will be confused with which tool
nix-shell
orcached-nix-shell
is actually in use or the versions combination is important?I think we can reach consensus here by set
CNS_LOG_LEVEL=trace
by default viaEnv::filter_or
so the output is actually what it was before, but with slightly different formatting, due to theenv_logger
library use. This would allow to switch all the logs related to cached nix shell by settingCNS_LOG_LEVEL=
which it a bit unfortunate for me but I am fine with that option if this sounds to you like something more appropriate.Let me know what do you think about this.
In the meantime, I redone that so it prints to
stdout
(in case of--version
argument only) and all the logging is still in place by default but can be turned off withCNS_LOG_LEVEL=
or downgrade the logging level likeCNS_LOG_LEVEL=info
, please have a look.Kind regards,
Oleg