Closed alansong21 closed 6 months ago
Are you working with the latest version of Blueprint? We upgraded some dependencies in our latest commit that fixed otel versioning issues.
Yes, I am using the latest version. Perhaps it has to do with the Go version? Initially I tried using Go 1.21.9, but some toolchains failed to install. I then used gvm to switch to Go 1.22.0, but then when I checked Go version in blueprint directory, it automatically changed the Go version to 1.22.1. Then, trying to build again led to error message saying Go version needs to be 1.22.0 not 1.22.1.
The issue I mentioned in the initial post is from when I ran with Go 1.21.9 and ignored the toolchains failing to build
This is what I saw when running go run wiring/main.go -w original -o build
:
[09:35:59.354] [slog/logger.go:303] ERROR: go: downloading go1.22 (linux/amd64)
go: download go1.22 for linux/amd64: toolchain not available
[09:35:59.354] [slog/logger.go:303] ERROR: unable to generate Hotel-original artifacts due to exit status 1
exit status 2
Checking the Go version:
als2005@node-1:~/blueprint/examples/dsb_hotel$ go version
go version go1.22.1 linux/amd64
Hmm, I can't seem to reproduce it locally atm. Will need to try it on a fresh machine so I'll need a couple of days to understand what's going wrong.
I think your docker compose is using a cached version of the containers which is perhaps preventing new fresh docker images with the right dependencies from being built. Can you remove all the containers from your docker registry and then try building again?
Yes, I removed all containers from the registry and ran docker compose build
again -- got the same error.
@vaastav OK, turns out I was still using go1.21 -- this issue is resolved now. Do you know why running go version
in the blueprint
dir showed go1.22 then? Does it have to do with the line toolchain go1.22.1
in the updated go.mod files?
@alansong21 Maybe, but I am not sure really. Usually, it's best to only have 1 version of go installed on your computer.
As everything is working, I am closing this issue now.
I followed the usual application build instructions in
examples/hotel_dsb
and randocker compose build
frombuild/docker
. I got the following output:Running the command
go get google.golang.org/grpc@v1.63.2
leads to the following:Building dsb_hotel was no problem previously. Any idea what may be causing this?