Skip to content
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

Closed
donbowman opened this issue Mar 7, 2019 · 9 comments
Closed

Strconv.atoi invalid syntax #816 not resolved by #832 #859

donbowman opened this issue Mar 7, 2019 · 9 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@donbowman
Copy link
Contributor

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:

Error: strconv.Atoi: parsing "": invalid syntax

#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

$ ./kustomize build /tmp/x
Error: strconv.Atoi: parsing "": invalid syntax

The syntax error is the missing - at the end of the op:

$ cat /tmp/x/default-issuer.yaml 
---
- op: add
  path: /spec/template/spec/containers/0/args/
  value: --default-issuer-kind=ClusterIssuer 
- op: add
  path: /spec/template/spec/containers/0/args/
  value: --default-issuer-name=letsencrypt

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.

@Liujingfang1
Copy link
Contributor

The line number if not available for Kustomize. I opened an issue in the library for json-patch. evanphx/json-patch#75

@donbowman
Copy link
Contributor Author

even so...
there's no change in the output w/ the PR. So its not clear how the PR solves the original issue?
can it at least talk about the object type its processing?

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 5, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 5, 2019
@donbowman
Copy link
Contributor Author

/remove-lifecycle rotten

the upstream code has had some improvement evanphx/json-patch#75 so changing the dependency would help.

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 5, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 3, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 2, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants