Andreas Hartmann (8f1aa630) at 17 Mar 16:53
Andreas Hartmann (64f1f0ff) at 17 Mar 16:53
Merge branch 'build/readme-refs' into 'main'
... and 1 more commit
Andreas Hartmann (8f1aa630) at 17 Mar 15:58
build: Fix README locations in workspace members metadata
... and 5 more commits
Andreas Hartmann (e2eb0463) at 17 Mar 15:58
Andreas Hartmann (2a49be68) at 17 Mar 15:58
Merge branch 'fix/debug-experience' into 'main'
... and 4 more commits
Make debugging easier by clarifying env variables for setting up log verbosity.
Make the --debug flag effective like it was meant to be from the beginning.
The online docs for the Env enum are now consistent with the code in that the
LogLevel member in Env now translates to environment variable
CNF_LOG_LEVEL, rather than RUST_LOG. The latter is still supported as
before, both variables are (and will remain) equivalent.
The --debug CLI-flag finally has an effect and increases log verbosity as
promised. This means you can now call cnf with --debug to quickly obtain
debug data without modifying your config or looking up the correct env variable
name.
I took a lot of wrong turns with the generic handling from tracing_subscriber
so this took surprisingly long. I have not been able to further simplify the
code in cnf::trace, nor have I been able to pull the flame graph setup into
the cnf::trace module entirely.
Andreas Hartmann (e2eb0463) at 17 Mar 15:43
test: Ensure that debug logging works as expected
Andreas Hartmann (19df9ff1) at 17 Mar 14:33
build: Fix README locations in workspace members metadata
Make debugging easier by clarifying env variables for setting up log verbosity.
Make the --debug flag effective like it was meant to be from the beginning.
The online docs for the Env enum are now consistent with the code in that the
LogLevel member in Env now translates to environment variable
CNF_LOG_LEVEL, rather than RUST_LOG. The latter is still supported as
before, both variables are (and will remain) equivalent.
The --debug CLI-flag finally has an effect and increases log verbosity as
promised. This means you can now call cnf with --debug to quickly obtain
debug data without modifying your config or looking up the correct env variable
name.
I took a lot of wrong turns with the generic handling from tracing_subscriber
so this took surprisingly long. I have not been able to further simplify the
code in cnf::trace, nor have I been able to pull the flame graph setup into
the cnf::trace module entirely.
Andreas Hartmann (7903f1ea) at 17 Mar 13:28
fix: Make logging env variables more obvious
... and 2 more commits
Andreas Hartmann (278624cb) at 17 Mar 07:20
Andreas Hartmann (278624cb) at 17 Mar 07:20
build: Bump project version to 0.6.0
Andreas Hartmann (2d01eeff) at 17 Mar 07:09
build: Bump project version to 0.6.0
Andreas Hartmann (278624cb) at 17 Mar 07:00
build: Bump project version to 0.6.0
Andreas Hartmann (8a020614) at 17 Mar 06:57
Andreas Hartmann (10b7937d) at 17 Mar 06:57
Merge branch 'fix/no-arguments' into 'main'
... and 1 more commit
Refuse to run without command arguments since in that case we have nothing to
go and find. This can happen, for example, when running cnf --debug or (if
the CLI hooks are installed) entering --debug in a shell prompt.
cnf should no longer crash with a weird error message when called like this:
$ cnf --debug
# Or, if you have the shell hooks installed
$ --debugInstead, it will now tell you that a required argument (the command to find) is missing.
Tests (and extra sanity check) are in place now.