Closed rashidakanchwala closed 1 month ago
@ankatiyar and @ElenaKhaustova - this issue crops up when the user tries to load the catalog from Kedro Framework using the private method
File "/Users/Livia_Pimentel/miniconda3/envs/cpib-models-test/lib/python3.10/site-packages/kedro/framework/context/context.py", line 187, in catalog
return self._get_catalog()
Do you know why this might be the case?
Closing as resolved.
@ankatiyar and I spoke with the user, it turns out their hooks were registering some custom resolvers. Kedro-Viz doesn't load hooks natively so the values were not getting filled hence the errors.
Using kedro viz run --include-hooks
resolves this issue.
Any way we could have made this easier to debug @SajidAlamQB @rashidakanchwala ?
Any way we could have made this easier to debug?
Their setup was unique so we needed a lot more context for the solution. Jumping on a call gave us that but maybe we could have asked the user for to explain in more detail.
I see the console output is exactly the same, with or without --include-hooks
. Maybe we should add a line that makes it more clear. Like
Running kedro-viz with hooks: mlflow, custom
or
INFO: Running kedro-viz without hooks, if you spot missing functionality try `kedro viz run --include-hooks`
Wdyt @SajidAlamQB ? (would merit opening a new issue)
I was also thinking that adding a hint about using --include-hooks
would help here
Thanks for the suggestion, @astrojuanlu and @ankatiyar. I agree, I like the idea of adding a hint/message, I’ll open a new issue to track this.
Description
The user encounters the following error when running kedro viz:
User is defining the below conf
In conf/base/catalog_globals.yml:
_path: ${path:}/${run_folder:}/
In conf/base/environ.yml:local:path: data/runs/
and User said
_It works fine with kedro run. We are running kedro run -p --env successfully._
Expected Result
Kedro-viz should run.
Actual Result
Kedro-viz throws the error
Here is the full traceback:
Your Environment
Include as many relevant details as possible about the environment you experienced the bug in:
Checklist