handle command return code in launch_gateway function #53590

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

peterxcli wants to merge 1 commit into apache:master from peterxcli:pyspark/check-command-return-when-launching-gateway

+8 −1

Member

peterxcli commented Dec 24, 2025

What changes were proposed in this pull request?

Stop waiting loop when the gateway process exits and raise PySparkRuntimeError on non-zero return codes.
Include command and return code in the error message for easier diagnosis.
Keep the existing check for missing connection info file.

Why are the changes needed?

Previously the loop could spin until the timeout even if the gateway had already failed.
Without surfacing the return code/command, diagnosing startup failures was harder.

Does this PR introduce any user-facing change?

No API changes; failure now surfaces earlier with clearer error details when the gateway process dies.

How was this patch tested?

Manual reasoning; no automated tests added (gateway startup is exercised by existing suites).

Was this patch authored or co-authored using generative AI tooling?

No.

github-actions bot added CORE PYTHON labels


          handle command return code in launch_gateway function

67a8f42

peterxcli force-pushed the pyspark/check-command-return-when-launching-gateway branch from 7f6a006 to 67a8f42 Compare

December 24, 2025 08:07

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels