-
Notifications
You must be signed in to change notification settings - Fork 903
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
Kedro Resume Information fails #3725
Comments
I think this is a great idea - We have this open PR #3719 which is close to merge - it makes sense to do this once that goes in (or maybe see if we can squeeze in the check there 🤔 ). |
Actually it may be solved by #3719 |
@MarcelBeining Is it possible to create an example with the spaceflights tutorial and provided the exact command to reproduce the scenario?
I am not sure if I am following, from which version it starts failing? My intuition is this related the dataset factory, #3719 is more of an incremental improvement of the existing resume suggestion. |
I go ahead to close this issue since there is insufficient information. Feel free to open a new ticket with some reproducible example if this still an issue. |
Description
Normally, when a kedro pipeline fails, it provides information about how to resume the pipeline (from which nodes to start). But since newer versions it always runs into an error in our cases.
I looked a bit into the case and found out it always happens when you have a dataset that is not defined in the catalog. This is then simply treated as a MemoryDataset (which is normal) but these MemoryDatasets are not in the catalog anymore (which is not normal), thus the error below happens.
Steps to Reproduce
Expected Result
You should get information of kedro in the console about how the error and how to resume from there
Actual Result
Your Environment
The text was updated successfully, but these errors were encountered: