Extensible Process Control API (pid and Signals)
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.5k
- Forks
- 636
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 7
Description
currently, fs2.io.process.Process wraps Java’s Process entirely but only exposes five basic methods (isAlive, exitValue, stdin, stdout, stderr). Java 9+ heavily expanded process management, but fs2 actively hides these new capabilities behind its minimal abstraction. Users frequently need to write out Process IDs to .pid files, or they want manual, fine-grained control to gracefully terminate specific child tasks without canceling the parent Resource.
We can expand the Process[F] trait with:
def pid: F[Long] (Fetch the OS process ID)
def terminate: F[Unit] (Send graceful SIGTERM)
def kill: F[Unit] (Send absolute SIGKILL)
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 at fs2.io.process.Process and the Java Process wrapper described in the issue. Check how the current five methods are implemented, then define the scope and completion criteria for exposing pid, terminate, and kill while preserving parent Resource behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala
- Domain
- api, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100