You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "wenjin272 (via GitHub)" <gi...@apache.org> on 2026/07/13 04:09:00 UTC

[PR] [python] Avoid forking MCP test server from PyFlink process [flink-agents]

wenjin272 opened a new pull request, #896:
URL: https://github.com/apache/flink-agents/pull/896

   Linked issue: N/A
   
   ### Purpose of change
   
   The MCP integration test starts its local MCP server with `multiprocessing.Process`. In GitHub Actions, this forks the already multi-threaded PyFlink and gRPC test process. The fork can corrupt the shared Py4J gateway, causing later PyFlink calls to fail with errors such as `Py4JError: org does not exist in the JVM`.
   
   Start each MCP server in a fresh Python subprocess instead, and wait for it to terminate during cleanup. This isolates the server from the PyFlink gateway and avoids leaking server processes between parameterized cases.
   
   ### Tests
   
   - `ruff check` and `ruff format --check` for the changed Python test
   - MCP integration tests for both server modes
   - MCP integration tests followed by `test_durable_execute_basic_flink` to verify the PyFlink gateway remains usable
   - Result: 3 passed
   
   ### API
   
   No public API changes.
   
   ### Documentation
   
   - [x] `doc-not-needed`
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] [test][python] Avoid forking MCP test server from PyFlink process [flink-agents]

Posted by "wenjin272 (via GitHub)" <gi...@apache.org>.
wenjin272 merged PR #896:
URL: https://github.com/apache/flink-agents/pull/896


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org