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

[BUG] fingerprint missmatch when running orchestrion go run <package>@latest with <package> not in go.mod #433

Closed
eliottness opened this issue Nov 28, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@eliottness
Copy link
Contributor

Describe what happened:

Running or building package with their full name and the @<version> suffix make it possible to bypass go.mod dependency resolution and acts as a quickfire way to download, build, and run in one go a Go binary. Except orchestrion fails when the said-package (here github.com/gohugoio/hugo) has no versions in the go.mod.

Here is the output:

/opt/homebrew/Cellar/go/1.23.3/libexec/pkg/tool/darwin_arm64/link: fingerprint mismatch: [google.golang.org/protobuf/proto](http://google.golang.org/protobuf/proto) has 053342eece2d492d, import from [github.com/bep/godartsass/v2](http://github.com/bep/godartsass/v2) expecting b47b4ca4b4e159fc

Describe what you expected:

I would expect the package to build fine and run.

Steps to reproduce the issue:

$ mkdir /tmp/test && cd /tmp/test
$ go mod init test
$ orchestrion go run github.com/gohugoio/hugo@latest
/opt/homebrew/Cellar/go/1.23.3/libexec/pkg/tool/darwin_arm64/link: fingerprint mismatch: [google.golang.org/protobuf/proto](http://google.golang.org/protobuf/proto) has 053342eece2d492d, import from [github.com/bep/godartsass/v2](http://github.com/bep/godartsass/v2) expecting b47b4ca4b4e159fc

Additional environment details (Version of Go, Operating System, etc.):
Version of orchestrion: v1.0.0
Tested on linux and MacOS

@eliottness eliottness added the bug Something isn't working label Nov 28, 2024
@eliottness
Copy link
Contributor Author

The workaround for now is to add the package to run to the go.mod file. Following the example given above this would require to run go get github.com/gohugoio/hugo@latest before doing orchestrion go run ...

@eliottness
Copy link
Contributor Author

Just as mentioned in #434, we are not able to resolve dependencies outside of the go.mod for now. The workaround cited above ⏫ will be the standard for now.

@eliottness eliottness closed this as not planned Won't fix, can't repro, duplicate, stale Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant