[Client] Print contents of stderr when command in StdioTransport fails to start #332

Activity

1. perk11

   added

   enhancementRequest for a new feature that's not currently supportedRequest for a new feature that's not currently supported

   on May 26, 2026
2. perk11 commented on May 26, 2026

   

   perk11

   on May 26, 2026

   Author

   More actions

   Additionally, it would be great if it would fail right after the process exits and wouldn't wait for the timeout.
3. wWzZb commented on Aug 14, 2026

   

   wWzZb

   on Aug 14, 2026

   Contributor

   More actions

   Hi, I'd like to work on this.

   I reproduced it on current main with a child process that writes to stderr and exits with code 7. StdioTransport keeps polling until the initialization timeout and only reports Initialization failed: Request timed out.

   The transport currently logs and discards stderr, and its polling loop never checks whether the child process has stopped.

   I'd keep the change scoped to Client\Transport\StdioTransport: retain a bounded tail of stderr, check proc_get_status() while polling, and fail the pending operation immediately with the exit status and captured stderr. Tests would use a real PHP child process and cover fast non-zero exit, stderr in the error, truncation, and the successful-response-before-exit case.

   Does that approach sound right? If so, I'm happy to send a PR.
4. chr-hertel

   added a commit that references this issue on Oct 12, 2026

   [Client] Report the stdio server's exit code and stderr when it dies

   ...

   This issue will close once commit b50d80f is merged into the 'main' branch.

   b50d80f
5. chr-hertel

   closed this as completedin #514on Oct 12, 2026
6. chr-hertel

   added a commit that references this issue on Oct 12, 2026

   [Client] Report the stdio server's exit code and stderr when it dies

   ...

   This issue will close once commit 000a055 is merged into the 'main' branch.

   000a055