JanWielgus / JanWielgus/PacketCommunication
Fix ESP8266WiFiComm available() method
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Now it always returns true, because there was problems with udp.available() method.
Try for example to use udp.parsePacket() method instead, but test it well (for example what will happen if someone use it several times, or at least if can be used twice in a row without read() method)
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
Start at the ESP8266WiFiComm available() method and inspect how its udp object is used. Compare udp.available() with udp.parsePacket(), then test repeated calls, including two calls in a row without read(); done means available() accurately reflects packet availability without always returning true.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100