GP
> Are you sure that the .proto file you are using is consistent with the one that the service was defined with? @murgatroid99 I am, yes. And FWIW, the other...
@murgatroid99 So the error is from [here](https://github.com/grpc/grpc-node/blob/e1e073546812aad622ad1f7ad5e83ddd46b9d98f/packages/grpc-native-core/src/client_interceptors.js#L691). When I stringify [`response.read`](https://github.com/grpc/grpc-node/blob/e1e073546812aad622ad1f7ad5e83ddd46b9d98f/packages/grpc-native-core/src/client_interceptors.js#L686), I get — ``` KEY-ef33408c3ce1ecbfb2e4!VALUE-ok-KEY-ef33408c3ce1ecbfb2e4 �����;�*test9: subjecttest9: reply ``` Dump of the buffer direct to a file — [output.txt](https://github.com/grpc/grpc-node/files/3594494/output.txt)...
@murgatroid99 There's more weird stuff happening. When I `Publish` this `Message` — ``` { offset: 0, key: 'S0VZLWFlZmNkYWFhNThhMDlhNmViYWYy', // b64 version of 'KEY-aefcdaaa58a09a6ebaf2' value: 'VkFMVUUtb2s=', // b64 version of 'VALUE-ok'...
@murgatroid99 By printing the deserialize error trace, I was able to trace the deserialization down to the `headers` map. Full stack trace — ``` Error [AssertionError]: Assertion failed at new...
I was finally able to trace it to the root cause! _wipes sweat from forehead_ The problem is when the `headers` map has an `undefined` value. The Go client reads...
@murgatroid99 Thanks for the pointers, I've further narrowed down the issue to a missing argument in the generated `_pb.js` file for deserializing map fields - see protocolbuffers/protobuf-javascript#43. If you're familiar...
https://github.com/protobufjs/protobuf.js/pull/1348 should fix this.
@gzuidhof Is your package published to the npm registry? I tried running – ``` npm install @guidhof/go-npm ``` but this doesn't work!
@gzuidhof Oops, so sorry! It works, thanks! Although, I wish to report an issue, but I notice the issue tracker isn't enabled for you repo. What would be a good...
Does anybody have current workarounds that will let us open the extension popup?