MarketSquare / MarketSquare/Rammbock
Problem with KW 'Client Receives Message' handling
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 64
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
Hello!
Could you please help about the following suspected Rammbock related issue (version 0.4.0.2 in use):
Sometimes the 'Client Receives Message' keyword makes timeout; see the following screenshot:
While from some Wireshark trace for sure the response message was coming from remote peer:
And in case repeated execution the sequencesometimes goes correctly, but randomly the same fails as above.
What is causing this and how to overcome?
Thank you!
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 reproducing the timeout with Rammbock 0.4.0.2 using the “Client Receives Message” keyword, comparing successful and failing repeated executions with the supplied Wireshark traces. Done means identifying why a response visible in the trace is missed and documenting or implementing a reliable resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100