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
If referencing a non-existing vss.json from the AppManifest.json and calling velocitas init -f the model lifecycle has this misleading output:
... > Running post init hook for 'vehicle-model-lifecycle'
Running 'install-deps'... done
Running 'download-vspec'... done
Running 'generate-model'... !
› Error: Program returned exit code: 1
Misleading, because the download-vspec should drop the error and not the generate-model.
Also, there is unspecific message if a non-supported VSS version is used (e.g. VSS version 4.0 at the moment).
Also, if model lifecycle fails during devContainer setup, the failure is not clearly visualize and could be quite easily overseen. This seems especially the case if using GH Code Space.
Steps to Reproduce
Change VSS reference in AppManifest to non-existing file
Run velocitas init -f
Expected Behavior
Error messages should clearly point out what the issue is
Possible Solution
No response
Additional Information
No response
Code of Conduct
I agree to follow this project's "Code of Conduct".
The text was updated successfully, but these errors were encountered:
Severity
Medium
What release version, tag or commit-hash did you use?
2ed763a
Current Behavior
If referencing a non-existing vss.json from the AppManifest.json and calling
velocitas init -f
the model lifecycle has this misleading output:Misleading, because the
download-vspec
should drop the error and not thegenerate-model
.Also, there is unspecific message if a non-supported VSS version is used (e.g. VSS version 4.0 at the moment).
Also, if model lifecycle fails during devContainer setup, the failure is not clearly visualize and could be quite easily overseen. This seems especially the case if using GH Code Space.
Steps to Reproduce
velocitas init -f
Expected Behavior
Error messages should clearly point out what the issue is
Possible Solution
No response
Additional Information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: