You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since v0.30 it seems that having GOFLAGS=-trimpath being set will affect Swagger. We updated go-swagger in our codebase and suddenly half of the spec was gone for no reason. After days of debugging and bisecting we found that GOFLAGS=-trimpath seems to be causing issues. The moment we unset it before running go-swagger, the problem goes away. We use Go 1.18.
I have no further insights as to why this happens, if anyone wants to check our debugging session you can look at kubermatic/kubermatic#10912. I just want to leave this here in case someone else gets bitten by this. Not even sure this is a bug, hence not opening a ticket for this. Maybe doing a go mod vendor before running go-swagger would also help.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Since v0.30 it seems that having
GOFLAGS=-trimpath
being set will affect Swagger. We updated go-swagger in our codebase and suddenly half of the spec was gone for no reason. After days of debugging and bisecting we found thatGOFLAGS=-trimpath
seems to be causing issues. The moment we unset it before running go-swagger, the problem goes away. We use Go 1.18.I have no further insights as to why this happens, if anyone wants to check our debugging session you can look at kubermatic/kubermatic#10912. I just want to leave this here in case someone else gets bitten by this. Not even sure this is a bug, hence not opening a ticket for this. Maybe doing a
go mod vendor
before running go-swagger would also help.cc @lsviben
Beta Was this translation helpful? Give feedback.
All reactions