You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: bind py4j callback server to a dynamic port to avoid 25334 collision
PythonCallback started the py4j callback server with no port argument, so
py4j bound the hardcoded default port 25334. Concurrent or repeated runs on
the same host using a lambda-based Check then failed with
"OSError: [Errno 98] Address already in use (127.0.0.1:25334)".
Start the callback server on port 0 and reset the JVM-side callback client to
the actually-bound port (the documented py4j pattern), fixing both the bind
collision and the "Error while obtaining a new communication channel" failure
seen when only port=0 was set.
Closes#86, #19, #7, #72, #156, #173, #198
0 commit comments