go mod vendor fails when module depends on jaeger

[wpcarro]

I originally reported this issue here: timescale/promscale#1374

$ go mod vendor -v # from promscale repo at 0.11.0
# github.com/jaegertracing/jaeger v1.33.0
## explicit
github.com/jaegertracing/jaeger/cmd/collector/app/sampling/model
github.com/jaegertracing/jaeger/cmd/query/app
github.com/jaegertracing/jaeger/cmd/query/app/apiv3
github.com/jaegertracing/jaeger/cmd/query/app/querysvc
github.com/jaegertracing/jaeger/cmd/query/app/ui
go mod vendor: pattern actual/*: no matching files found

I'm posting here in case this is a bug with jaeger. As I said in the other issue, I'm a golang n00b, so I'm not sure who's (if anyone) is at fault. I'm not even sure if my expectations are correct. I just expected to be able to call go mod vendor on the promscale repo and have that command succeed.

Any ideas?

[yurishkuro]

it's probably because of this:

jaeger/cmd/query/app/ui/actual.go

Line 28 in f9992f7

//go:embed actual/*

There is no actual/ directory in the git repo, it is only created when the real UI assets are built and copied there. I created #3698, please try updating promscale to use that branch & see if it fixes your issue.

[wpcarro]

Thanks for the quick response. Calling go mod vendor is now working as expected :)