MarketSquare / MarketSquare/Rammbock
message_stream.get function will drop into endless loop
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 64
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
We found robot can not stop sometimes. After research found the core reason is that message_stream.get will drop into endless loop when no expected message found and socket never empty (receive data persistently).
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 by locating the message_stream.get entry point and reading how it handles socket data when the expected message is absent. No file or test is named in the issue; done means the robot can stop and get no longer loops endlessly while data continues to arrive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100