-
Notifications
You must be signed in to change notification settings - Fork 242
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
go-getter failed in some cases #257
Comments
Hey @Shell32-Natsu, thanks for reporting, quick question; are these bugs happening in a stable manner ? Or is this random ? Because if this is randomly happening this could may be due to the fact that the getters are in a map on the |
Yes these issues can be reproduced stably. |
See argoproj/argo-cd#3814 Kustomize issue: kubernetes-sigs/kustomize#2538 go-getter issue: hashicorp/go-getter#257
See argoproj/argo-cd#3814 Kustomize issue: kubernetes-sigs/kustomize#2538 go-getter issue: hashicorp/go-getter#257
It looks like query parameters are being put on the path which results in a percent encoded
I am working around the issue using an alternate implementation of the GitHub detector that preserves the query parameters. |
Some sub directories cannot be gotten
Meanwhile some sub dirs work
ref
doesn't work when get sub directoryForce protocol doesn't work with sub dir
In my experiments,
//
and/
have same behavior. Is that expected?The text was updated successfully, but these errors were encountered: