Closed jonasbadstuebner closed 5 months ago
Failed to parse input
is also an error I can produce at will by dumping the binary output into a protoc --decode_raw
with the dart plugin. If this helps?
test with protoc -I=lib/protos --dart_out="grpc:lib/protos/" lib/protos/google/protobuf/empty.proto --plugin=$HOME/.pub-cache/bin/protoc-gen-dart
Does someone see something off?
That the plugin output starts with \020
is kind of suspect, as that is the space character.
We’ve seen similar issues with extra output being injected into one or the other protoc
or our protoc-gen-go
.
That there might be some sort of extra output is about the only help or hint that we can really provide here. I don’t know enough about the protoc-gen-dart
code to say anything about what output it should be generating.
Thank you so much for the hint! It was not the space, but your hint sparked a new idea and it turned out to be very likely related to a wrapper tool I am using. It adds an additional newline at the end of the dart plugin output.
I'm closing this, thank you very much again!
Hello,
I am getting a
plugin output is unparseable
error and I am really stuck. I know that the dart plugin is not supported by this repository here, but I wanted to ask for some help with debugging the issue, since I don't even know, why it is not working. Can someone guide me to how I could debug what is actually wrong with the output of the plugin?protoc seems to not have great debugging options.
I can generate Java code with no problem, but I don't know why this works and the dart plugin does not work. Somewhere inside protoc something is failing and I cannot tell, why or what. Is there a way to "look inside" protoc and know at which point it is actually dying?