Closed stapelberg closed 2 months ago
Notably, it works with github.com/bufbuild/protocompile v0.13.0, but panics only when I
go get github.com/bufbuild/protocompile@v0.14.0
.
Oof. Definitely a regression then.
GitHub auto-closed this because a fix in another repo referenced this issue and was merged. But this issue won't actually be fixed until that other fix is released and then pulled into this module.
Feel free to tell me that I’m holding it wrong, but I figured I’d report this issue.
We have a pipeline with which we analyze all .proto files in our repo. The pipeline parses proto files using the
InterpretOptionsInUnlinkedFiles
andIncludeSourceCodeInfo
options, so that we can work with some custom options we’re using.I noticed that the pipeline panic'd when processing a specific .proto file, but that behavior only started happening recently.
I distilled it down into the following test case:
…which panics with the following backtrace:
Notably, it works with github.com/bufbuild/protocompile v0.13.0, but panics only when I
go get github.com/bufbuild/protocompile@v0.14.0
.Also, the panic disappears when I additionally enable
ValidateUnlinkedFiles
, presumably because execution doesn’t get as far anymore in that case.Is it expected that we need to enable
ValidateUnlinkedFiles
in order for option interpretation to work, or is this a regression?Thanks