You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a project which uses config templates. Every now and then the dev console (garden dev) will crash with the error:
Cannot read properties of undefined (reading 'inputsSchema')
At a glance I think this only happens after the Garden config has been modified (and Garden prints the Config change detected. Project will be reloaded when the next command is run.)
This usually happens when I run commands from within the console or on events triggered by the dashboard if that's open (some of these events trigger internal Garden command where the config resolution fails).
Expected behavior
It doesn't crash.
Reproducible example
I haven't been able to pinpoint exactly when this happens so kind of hoping someone can spot the issue without a solid repro. But it does strike me as some config resolution race condition since it doesn't fail consistently.
Open the web dashboard on the live page (if only to have it trigger internal Garden commands which may surface this)
Tweak the actual Garden config (e.g. re-naming an action or adding a new one)
Wait for the dashboard to request a new graph via the loadConfig ws message which is called when the config changes, or run some commands from within the console (e.g. validate)
Observe as it crashes. Most likely. Sometimes.
Workaround
No known workaround, it basically makes the dev command un-usable for projects that use config templates.
Your environment
garden version Latest main as of writing.
The text was updated successfully, but these errors were encountered:
Garden Bonsai (0.13) Bug
Current Behavior
I have a project which uses config templates. Every now and then the dev console (
garden dev
) will crash with the error:Cannot read properties of undefined (reading 'inputsSchema')
At a glance I think this only happens after the Garden config has been modified (and Garden prints the
Config change detected. Project will be reloaded when the next command is run.
)This usually happens when I run commands from within the console or on events triggered by the dashboard if that's open (some of these events trigger internal Garden command where the config resolution fails).
Expected behavior
It doesn't crash.
Reproducible example
I haven't been able to pinpoint exactly when this happens so kind of hoping someone can spot the issue without a solid repro. But it does strike me as some config resolution race condition since it doesn't fail consistently.
Your best bet to repro would be to:
garden dev
in e.g. this example which uses config templates.loadConfig
ws message which is called when the config changes, or run some commands from within the console (e.g.validate
)Workaround
No known workaround, it basically makes the dev command un-usable for projects that use config templates.
Your environment
garden version
Latest main as of writing.The text was updated successfully, but these errors were encountered: