Ipc\connect is not part of the IpcHub interface
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 859
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
This essentially makes the entire IpcHub interface useless, as custom IPC implementations (i.e. IPC over FIFO, IPC over shared memory, et cetera) cannot override the logic of Ipc\connect() without also uselessly reimplementing the ProcessContextFactory and process-runner.php.
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 IpcHub, Ipc\connect(), ProcessContextFactory, and process-runner.php, then trace how the current connection is selected. Check existing interface implementations and tests to understand the smallest change that lets custom IPC implementations supply their own connection without reimplementing process setup. Done means the relevant custom IPC path works and its tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100