Windows USR signals
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 9.5k
- Forks
- 1.7k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 25
Description
Since the following signals are not available on Windows
USR1 - Immediately kill child but don't exit
USR2 - Don't start to process any new jobs
is there any other way to control a worker (stop/start processing jobs)?
Shall we use different SIGNALS available on Windows only for this job?
I will appreciate any help.
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
Start by locating the worker signal-handling and job-processing control paths, then compare them with the signals available on Windows. Define a Windows-compatible way to stop or start processing and document or test the expected worker behavior; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100