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

go install: cannot load embed: malformed module path #201

Open
michas2 opened this issue Aug 14, 2022 · 1 comment
Open

go install: cannot load embed: malformed module path #201

michas2 opened this issue Aug 14, 2022 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@michas2
Copy link

michas2 commented Aug 14, 2022

The Readme is missing a clear example what subcommands should be issued in which order.

I went to a folder containing a single helm release and did cr package which created .cr-release-package fine.

When I do cr upload later I get:

Error: error creating GitHub release burp-suite-enterprise-edition-2022.7.0: failed to upload release asset: /home/michas/flux/eks-charts/charts/burp-suite-enterprise-edition/.cr-release-packages/burp-suite-enterprise-edition-2022.7.0.tgz
: POST https://github.vodafone.com/api/uploads/repos/VFDE-Solstice-Systemintegration/eks-charts/releases/41955/assets?name=burp-suite-enterprise-edition-2022.7.0.tgz: 422  []

The server seems to answer 422 without any reason. 😐

Uploading artifacts manually using curl works fine.

Unfortunately I don't have access to the server logs. Also I am not aware of any debug output available in cr.

Therefore I tried to build from source to add some debug output myself.

I followed the instruction in the Readme and cloned the source. However the install step fails:

$ go install ./...
build github.com/helm/chart-releaser/cr: cannot load embed: malformed module path "embed": missing dot in first path element

I'm not using go a lot, so maybe there is an easy solution, but I was expecting the instructions in the Readme to work out of the box.

Are you able to helm me with the install, or even with the 422/debug?

@cpanato cpanato added help wanted Extra attention is needed enhancement New feature or request labels Aug 17, 2022
@michas2
Copy link
Author

michas2 commented Aug 24, 2022

I now got access to the server logs. Looks like the cr tool is trying to push the artifact 3 times. The first time the server creates the artifact and returns 201, but then the tool will try to upload the same artifact 2 times more, which will result in a 422, because the artifact is already present.

I also found that my version of go was too old. Therefore I got the "cannot load embed" error.
I'm able to debug now. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants