Robustify ping parser
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- networking
Research direction
Start by locating the current parser and the code that processes the current messages payload. Determine how lost bytes can cause new messages to be missed and where fixed-width payload lengths are validated. Done means the parser recovers from byte loss and rejects payloads with invalid fixed-width lengths, with corresponding coverage added where the project’s parser tests live.
Written by the indexing model from the issue text.
Description
Add some sort of concurrent parser or recursion to pick up new messages in what the current parser would think is the current messages payload, in the situation of bytes lost in transit.
Also sanity check payload length for fixed-width messages.
- Dominant language
- C++
- Stars
- 19
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
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.
More from bluerobotics/ping-cpp
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bluerobotics/ping-cpp#66 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
bluerobotics/ping-cpp#69 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
bluerobotics/ping-cpp#68 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
bluerobotics/ping-cpp#65 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
bluerobotics/ping-cpp#57 ·
All issues in bluerobotics/ping-cpp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·