Replies: 2 comments 1 reply
-
It is just a decision I use in a new major draft😅 |
Beta Was this translation helpful? Give feedback.
0 replies
-
So, you can find it in 0.1.5.14 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I've been working with the code and noticed an opportunity to improve our error logging and debugging experience.
Current Code Handling:
Below is how our current code handles and logs exceptions:
Propan/propan/brokers/_model/broker_usecase.py
Lines 614 to 642 in fd243da
In its current state, the code logs exceptions but doesn't include a traceback or the log_context that could potentially be very useful for debugging.
My Proposal:
To enhance our error logging, I suggest adding the traceback to exception logs, and to provide extra context, include log_context. Here's a potential way of doing it:
By incorporating these, we could have better insights into errors which could streamline our debugging process.
Looking for Suggestions:
The part I am pondering over is how to allow users to opt in or out of this additional logging behavior, maybe using an environment variable.
I would love to hear your thoughts and any potential solutions for this part. Thank you in advance for your input.
Beta Was this translation helpful? Give feedback.
All reactions