Repository navigation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat(cli): report the real exit code and really stop what uipath server runs #1842
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.
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
base: main
Are you sure you want to change the base?
feat(cli): report the real exit code and really stop what uipath server runs #1842
Changes from 1 commit
c2d56aac9b307d842268bFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
run/debug/eval drive their own event loop on the server's worker thread. They now publish it through run_execution_loop to an ExecutionControl, so a stop cancels the execution's root task and the runtime unwinds cooperatively, still writing its result. stop_execution backs both IPC StopJob and the new POST /jobs/{key}/stop. It cancels the root task, waits a grace period, cancels every task on the execution's loop, and answers False if it is still running, because it is blocked in a call that only ending the process can interrupt. forceStop shortens the waits. A queued execution is dropped before it runs. A stop that targets another resume version, or an unknown key, answers True: that run is not running. The lock, env and cwd are no longer handed on while the execution's thread still runs. A cancelled caller (a dropped IPC connection, a shutdown) stops the execution and re-raises only once the thread has exited, and the job scope's teardown completes before the env is restored. A stopped execution ends with exit code 143 and "Stopped on request"; a CancelledError it raised on its own is reported as an unexpected failure. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Uh oh!
There was an error while loading. Please reload this page.