-
We rely solely on __debugbreak(), MSVC's debugger and printf() to get the job done.
This is bad. It must be addressed.
-
We should add logging to help with debugging. Since error handling is non-existent, this has even higher importance than usual. Thanks to Leo Broska for the suggestion.
-
There are certain cases where it might be nice to warn with a logger (e.g. network ambiguity during decoding). Is using the `logging` module consistent with design goals here?
-
Log the shit out of everything. EVERYTHING.
-
In order to better understand the internal flow when debugging or developing, it would be very helpful to have run-time switchable logging, including debugging and tracing levels.
For a simple and …
-
Submitted by: tectsoft (tectsoft)
Votes: 4
SFID: 1108199#⁠
Submitted By: tectsoft
Would be nice to have improved logging facilities\.
\- Log failed connections\. \(see request 1107907 as we…
-
-
## Benefit to the Veteran
As a Veteran, I want to be confident that the VA is monitoring failures, so that issues can be resolved quickly with little to no impact to Veterans.
## Scope
- As part of t…
-
Currently `salt/log` package tries to abstract Logrus and Zap into a common formatted-logger interface (i.e., `Infof(msg string, args ...any)`, etc. ). While `logrus` is designed as a formatted-logger…
spy16 updated
2 years ago
-
Currently, the print server and the Lua code have different log level definitions as well as different log message formatting.
Both lack a proper facility mechanism, making it sometimes hard to determ…