MarketSquare / MarketSquare/robotframework-requests
Second session's timeout overwrites the first session's timeout
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 512
- Forks
- 283
- PR merge metrics
- No merged PRs in 30d
Description
It is expected behaviour that sessions have its own timeouts.
Though the last used timeout in `Create Session` keyword overwrites the timeout value for all previous sessions.
Please check test case below.
```robot
*** Settings ***
Library RequestsLibrary
*** Test Cases ***
Test Case To Check Request Session Timeouts
[Tags] check_timeouts
RequestsLibrary.Create Session session_5 https://httpbin.org timeout=5
RequestsLibrary.Create Session session_2 https://httpbin.org timeout=2
RequestsLibrary.GET On Session session_5 /delay/3
```
Used versions:
```
Python 3.9.13
requests 2.25.1
robotframework-requests 0.9.7
robotframework 7.1
```
Contributor guide
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 the issue with the supplied Robot Framework case, focusing on the Create Session and GET On Session keywords and the listed Python, requests, and library versions. Trace how each session's timeout is stored and used, then verify that session_5 still permits its configured timeout after session_2 is created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100