You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 12, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on May 12, 2026. It is now read-only.
First of all, I'd like to say, awesome library, kudos any many thanks for writing this 😃 😃 😃
I think I've come across a bug when decoding a message. According to the documentation I can pass in a length to the Message.decode function. However, the length is ignored and instead it tries to decode the whole buffer.
This is the code:
As you can see, the length argument is not used anywhere in this function, nor passed along to T.decode(). This seems like a bug to me. Or am I missing something here?
Oops, I accidentally put this bug report in the wrong repo, should have been the Protobuf repo. My bad, sorry. I just found out that it's a duplicate of protobufjs/protobuf.js#436 and it has actually been fixed on the master of protobuf, but not yet on the 5.0.1 npm version.
Are there any plans of updating protobuf on npm?
Cheers
Activity
IjzerenHein commentedon Sep 11, 2016
Oops, I accidentally put this bug report in the wrong repo, should have been the Protobuf repo. My bad, sorry. I just found out that it's a duplicate of protobufjs/protobuf.js#436 and it has actually been fixed on the master of protobuf, but not yet on the 5.0.1 npm version.
Are there any plans of updating protobuf on npm?
Cheers