-
Notifications
You must be signed in to change notification settings - Fork 908
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better Error Logging #3651
Comments
@lordsoffallen Can you show an example and explain what would you preferred to see instead? And please include the version of Kedro |
Sure, this is what I get now (created a dummy error function).
|
What I would like to have: (couple of more from kedro at the beginning would be okay.)
|
@noklam Basically, a possible option to turn off kedro stacktrace when an error happens. Now I have to scroll up to find when an error occured. It would be really nice to have simpler logging in this case. I was gonna try something with |
For reference, this is the log I see in 0.19.2. Current log(
If I try to suppress
The change is adding Line 43 in 527108c
|
This is already an improvement to me. Completly surpassing may not help if a user had kedro related errors in the code. An option in the logging file to enable this would be super useful. If we can do something like the following that would be best case I suppose:
I might be missing some cases but that's what I have in mind. Even a easy option to suppress this would be cool. (I don't know if this can be done on user side or not) |
@lordsoffallen Technically you can already do that. Here is an example of logging. The optional argument can be configure via Lines 42 to 60 in 527108c
|
Thanks for the link.
then it should work as I expect ? Regarding the PR, I don't have much experience with logging nor rich library so not sure how much I can contribute here but if I find something that works I'd be happy to share this here somehow. |
With 0.19, this is true that logging.yml is no longer pick up automatically. There is a reason why we need to use environment variable and de-couple it from ConfigLoader. Personally I don't really like this, and may even consider this as a bug because in This is why I proposed #3446 to change this. For your second question, you cannot mock Kedro because you need Kedro to run your pipeline. You can create a custom rich handler, change the "suppressed" settings and register it in
This is fine! If you can comment on the relevant issues and share your insight, it would already helped us prioritise and design a generic solution a lot. |
Description
Usually when my code errors out, the stack trace is quite long and half of them coming from kedro. So far, kedro stack trace isn't really helping when it comes to debugging as issues are on my code. It would be quite nice if we can disable kedro stack trace so when something errors out regarding user code, i.e executing the node function, then only shown where the code fails.
Context
Possible Implementation
Possible Alternatives
The text was updated successfully, but these errors were encountered: