-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
better message on syntax error when parsing JBP_CONFIG_OPEN_JDK_JRE #268
Comments
We can definitely handle the exception a little bit better than it currently is. As far as the |
Pivotal Tracker Issue: https://www.pivotaltracker.com/story/show/111019418 |
How about the following message?
Note that |
Yeah, I agree. My thought was that we'd simply catch the YAML parsing exception, give it some context and print the message. So that seems to match. |
You're right @glyn |
Thanks. |
Fixed at master. |
When I added the following line in
env:
section of the manifest yaml fileI got the following error when pushing an app
Then when I change the env variable to
then the deployment succeed as expected.
Notice the space after the colon in
native: 10
, compare tonative:10
in the first example.I think this can be generalized to :
the separator between an attribute name and an attribute value is required to be ": " (colon + space),
when the separator is ":" (colon) the buildpack will fail with the ruby error and stack trace during staging
This is a user input problem, but it would be nice to have this case be handled with an insightful error message, and no stack trace.
The message could be as simple as stating :
Syntax error while parsing env variable JBP_CONFIG_OPEN_JDK_JRE : found unexpected ':' while scanning a plain scalar at line 1 column 67
The status
Failed to compile droplet
andBuildpackCompileFailed
are also alarming and misleading, as they could be interpreted as a problem either in the buildpack or on the cloudfoundry service.The text was updated successfully, but these errors were encountered: