-
Notifications
You must be signed in to change notification settings - Fork 34
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
Handling of Exceptions in MLPipeline #377
Comments
Thank you already for your support. My suggestion would be to just call |
Hi @daniel-ressi, you're not the first one to notice this behaviour. Unfortunately, kedro filters your pipeline to suggest a resume scenario, and this breaks However, given how annoying this stacktrace is, I am considering changing the behaviour and only issuing a warning. The risk is that some people will run their entire pipeline before noticing I will try to find a way to not hinder the entire stacktrace, but I have no straighforward solution for now, sorry. |
thanks for you swift response. Is the issue that kedro's resume scenario would relate to to running only the training pipeline and not the I guess ideally it would be possible to disable the resume scenario suggestion for a PipelineML run, but this seems not possible as it's not called through a hook butwith the Runner. Eitherway great work @Galileo-Galilei ! |
Closed by #601 |
Description
Errors in the MLPipeline are overshadowed by a NotImplementedError Exception, which makes debugging more complex than necessary
Context
This bug occurs only if there is an Exception in the MLPipeline.training pipeline.
It is not critical as the relevant Error message is still shown above
Steps to Reproduce
If required I can prepare a better example, but this should actually be enough to reproduce the issue.
raise ValueError("My debug message")
to any node which is part of an MLPipeline (training) using kedro > 0.11Expected Result
I expect a ValueError to be raised with "My debug message". In addition kedro provides a resume from nodes preview functionality. And this is actually cause of the issue.
Actual Result
During handling of the above exception, another exception occurred
Your Environment
Include as many relevant details about the environment in which you experienced the bug:
kedro
andkedro-mlflow
version used (pip show kedro
andpip show kedro-mlflow
): 0.18.3 and 0.11.4python -V
): 3.9Does the bug also happen with the last version on master?
Yes, tried it out
The text was updated successfully, but these errors were encountered: