What is the reason for handling interrupted system calls (EINTR) throughout the code?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- documentation, networking
Research direction
Read the socket-function and select call sites in the single-header C++ HTTP request class, then trace how EINTR is handled around them. Done means explaining the reason for these checks and documenting whether the current handling is necessary.
Written by the indexing model from the issue text.
Description
I noticed that you are checking for EINTR across all socket functions. Can you explain why? As far as I understand, in order for a system call to be interrupted, the following conditions must be met:
- The process must be blocked by a system call (which only occurs in select since you are using a non-blocking socket).
- The process must be catching signals, but the code does not catch any signals.
- Dominant language
- C++
- Stars
- 969
- Forks
- 200
- 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 elnormous/HTTPRequest
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
elnormous/HTTPRequest#79 · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
elnormous/HTTPRequest#77 ·
-
A couple of ideas Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
elnormous/HTTPRequest#76 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
elnormous/HTTPRequest#75 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
elnormous/HTTPRequest#74 · 1 comment ·
All issues in elnormous/HTTPRequest
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·