-
Notifications
You must be signed in to change notification settings - Fork 112
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
Unsupported Interpolation Type Error
in Kedro-Viz with OmegaConf
#2142
Comments
@ankatiyar and @ElenaKhaustova - this issue crops up when the user tries to load the catalog from Kedro Framework using the private method
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 |
Any way we could have made this easier to debug @SajidAlamQB @rashidakanchwala ? |
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
or
Wdyt @SajidAlamQB ? (would merit opening a new issue) |
I was also thinking that adding a hint about using |
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 <PIPELINE_NAME> --env <ENVIRONMENT_NAME> 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
The text was updated successfully, but these errors were encountered: