-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
This is how to turn on INFO-level logging for jax right now:
```
from absl import logging
logging.set_verbosity(logging.INFO)
```
It'd be better to have an env var like `JAX_LOG_LEVEL=INFO` so …
-
-
https://swimburger.net/blog/dotnet/changing-serilog-minimum-level-without-application-restart-on-dotnet-framework-and-core
Blocked by: v4
Blocked by: #486
-
### Use Case
I'm debugging an adapter which uses this adapter runtime. I'm getting a "File not found" error but the error lacks additional context and I'm looking for more logs to figure out what's g…
-
**Is your feature request related to a problem? Please describe.**
I was trying to use `gum log` as part of my shell script function loggings. But doing so with the `gum log --level debug` will alwa…
-
The current logger in `boilerplate` only supports `Printf` with no logging levels. We should replace it with a logger that supports logging levels so that user can control the verbosity of the logs.
-
My JMH runs are full of
```
09:49:54.977 [megacorp.LoadTest.searchComplex-jmh-worker-1] DEBUG org.apache.http.headers
```
The documentation does not show how to change the log level and on the ap…
loxal updated
3 weeks ago
-
At the moment, logging is a bit random and way too verbose even on the INFO level. Now that we have a decent logging framework, we need to make it more helpful.
-
Instead, we could add an optional `level` field to the global log function:
```js
log("Hello", level: std.LogLevel.VERBOSE)
```