-
We should use the `logging` module instead of `print` - it allows for greater control and flexibility.
-
## Environment
**Liquibase Version**: Any
**Liquibase Integration & Version**: Any
**Liquibase Extension(s) & Version**: Any
**Database Vendor & Version**: Any
**Operating System Type…
-
At the agent start, the stdout of the agent shows multiple banner messages and output from print statements.
Having noisy logs makes it more difficult to identify quickly actual problems.
Expec…
-
I see that there are a lot of print statements build into the library (e.g. `print(f'Factorized version: lnA at time {t}: {lnA}')` in pymdp/algos/mmp.py). It would be preferrable to use a canonical l…
-
Hello,
for my use case it is important to log the exact query executed, which is by default not possible with prepared statements, as I unterstand. (You can only see the prepared statement before the…
-
Often for quick debugging at a beamline staff/users will inject temporary print statements into plans. When doing this under plans run by BlueAPI the output are not appearing in the logs, either in gr…
-
### Name and Version
bitnami/postgresql 15.5.23
### What architecture are you using?
amd64
### What steps will reproduce the bug?
1. Kubernetes 1.29 (doesn't matter)
2. Install chart w…
teu updated
10 minutes ago
-
Suggestion: Add some logging statements lower that INFO level, to illustrate the use of various logging levels.
-
Using Android Studio and performing `debug("foo")` followed by `debug("bar")` only bar shows up in the device monitor. So, I had to put a `debug("")` in the onCreate, which is unfortunate or I am miss…
-
This should be pretty straight forward: Replace all `print` statements with a logger