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
Strconv.atoi invalid syntax #816 not resolved by #832 #859
Comments
The line number if not available for Kustomize. I opened an issue in the library for json-patch. evanphx/json-patch#75 |
even so... |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten the upstream code has had some improvement evanphx/json-patch#75 so changing the dependency would help. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
In #816 I gave an example of a type of syntax error in the input yaml that lead rise to a non-useful error. In this case, it did not indicate the file or line or object or type of error, it just said:
#832 was created, ostensibly to address this.
However, it does exactly the same thing with input file as given in #816 .
I fetched from master, verified commit 78cbff1 was present, ran
go build
, and then./kustomize build /tmp/x
The syntax error is the missing
-
at the end of the op:So I don't think this PR addresses the issue, the behaviour is unchanged.
My expectation is that I get file:line information, something useful I can go and find my syntax error. Its too complex to binary search down otherwise.
The text was updated successfully, but these errors were encountered: