mafintosh / mafintosh/protocol-buffers
Versions 4.0.4 & 4.1.0 both fail to run correctly on node-red 0.20.5-rpi
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 760
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
protocol-buffers enabled us to create a pure nodejs client for Eclipse Kapua - a much lighter alternative to Kura.
With node-red moving to 0.20.5 we wanted to be able to leverage all the great new features but both versions 4.0.4 & 4.1.0 of protocol-buffers fail to run correctly on node-red 0.20.5-rpi.
On receiving proto buf encoded messages from Kapua, protocol-buffers throws exceptions
- Error: groups are not supported
- Error: invalid wire type 6/7
The same kura message proto file is able to correctly support decoding of messages from Kapua when running on 0.19.x of node-red.
Note that **encoding** to protobuf for outbound messages seems to work correctly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce inbound Eclipse Kapua protobuf decoding with protocol-buffers 4.0.4 and 4.1.0 on node-red 0.20.5-rpi, then compare it with node-red 0.19.x where the same kura message proto file works. Trace the decoding path around the reported group and wire-type exceptions. Done means inbound messages decode without exceptions while outbound encoding remains functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100