Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Plugin output is unparseable

See original GitHub issue

Hello,

I’m hitting a problem with my plugin when the generated code gets larger than a certain amount. I’m getting the following error:

Plugin output is unparseable: \020\001z\266\302\036\n\020service.twirp.tsz\240\302\036
{content_removed}

you can reproduce this simply by trying and returning a large string in the content of a file

"hello".repeat(100000)

I suspect it is something to do with the max buffer size, but so far I haven’t found anything to increase that. Any idea?

Issue Analytics

State:
Created 2 years ago
Comments:11 (11 by maintainers)

Top GitHub Comments

1reaction

timostammcommented, Jul 26, 2021

Thank you for investigating this 🙏

I’d say the workaround belongs into plugin-base, even if it needs some dirty casts. PR is most welcome!

1reaction

timostammcommented, Jul 26, 2021

Do you know how to reproduce?

This works for me:

mkdir issue134

cd issue134

cat <<EOF > x.proto
syntax = "proto3";

service authentication {
  rpc A1(Am) returns (Am);
  rpc A2(Am) returns (Am);
  rpc A3(Am) returns (Am);
  rpc A4(Am) returns (Am);
  rpc A5(Am) returns (Am);
  rpc A6(Am) returns (Am);
  rpc A7(Am) returns (Am);
  rpc A8(Am) returns (Am);
  rpc A9(Am) returns (Am);
  rpc A10(Am) returns (Am);
  rpc A11(Am) returns (Am);
  rpc A12(Am) returns (Am);
  rpc A13(Am) returns (Am);
  rpc A14(Am) returns (Am);
  rpc A15(Am) returns (Am);
  rpc A16(Am) returns (Am);
  rpc A17(Am) returns (Am);
  rpc A18(Am) returns (Am);
  rpc A19(Am) returns (Am);
  rpc A20(Am) returns (Am);
}

message Am {}
EOF

npm init -y

npm i @protobuf-ts/plugin@next

npx protoc -I . x.proto --ts_out .