-
Should we introduce a framework for logging debugging information in the uutils?
In my eyes it would make debugging of issues in general but especially on CI much easier.
I think there should th…
-
### Description
Currently, our logging framework utilizes two separate configurations for handler setup: one within the `LoggingSystem` and another within each individual handler. This dual configurat…
-
## As a developer I want to...
be able to see which events log messages
## So that...
I can understand what is happening during code execution.
## Context
We have a lot of code and lots of mo…
-
pyroscope-java currently uses a custom logger implementation.
I'd like to propose the usage of a dedicated logging framework like SLF4J. What do you think?
-
We should give better insights and control about what exactly is happening.
-
We are mostly just using the `logDev` method everywhere. We should really add a logging framework with an adjustable log level.
-
Maybe more of a question for @charleskawczynski @simonbyrne but any suggestions for a logging library? It's probably a good software practice to move away from `print`/`@printf` statements to a loggin…
-
I am writing so many freaking `console.debug()` statements its crazy. We should implement a structured logging framework.
I don't want to deal with JSON output (even though that may end up being an…
-
Original proposal:
> - discovering tests
> - running them
> - mocking external dependencies
Revised proposal (see thread below): implement a logging framework on top of two different platforms…
-
### Description:
view.py's route logging system through `route_log` in the C API is *extremely* slow. Basically, with the new PyAwaitable vendor on the `reactpy` branch, view.py is slower than pretty…