Closed maoueh closed 1 year ago
I can at least repro with the whole project. This seems quite curious.
Huh… I found the problem. https://github.com/streamingfast/sf-ethereum/blob/develop/proto/google/protobuf/timestamp.proto#L37
I can confirm that changing the go_package
on that proto file fixes the imports.
🤦 oh gosh, didn't realized with had a committed version of the timestamp.proto
file, thanks for spotting that and sorry for the trouble.
What version of protobuf and what language are you using?
What did you do?
On our project, I had to re-generate the Golang protobuf bindings, it appears for some reason I fail to understand right now that it generates well known types pointing to old package
github.com/golang/protobuf/ptypes/timestamp
.What did you expect to see?
No changes to the
timestamp
well known generated types. I tried to replicate using a trimmed down version of our repository but did not succeed to reproduce.What did you see instead?
Git diff shows that
timestamppb "google.golang.org/protobuf/types/known/timestamppb"
has changed totimestamp "github.com/golang/protobuf/ptypes/timestamp"
.Anything else we should know about your project / environment?
I tried hard to replicate it on a trimmed down version of project, started with just a
type.proto
directly but every time it renders it with.Even tried again back with
protoc
3.19.4 andproto-gen-go
version 1.25.0, 1.26.0, 1.27.0 and 1.28.0 but every time I get the same thing on this project.Any clues to create a trimmed down reproducible repo would be appreciated.