fix(server): expose stopped task results - #530
Merged
Merged
Conversation
Contributor
Author
|
Coverage verification:
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Contract
Stopped tasks now expose total_runs, success_runs, and full details instead of hiding retained results behind a null result.
TDD
The first cancellation regression failed on origin/main because TaskManager.get_status() returned a null result. The production change only extends the existing terminal-result projection to TaskStatus.STOPPED.
Verification
Scope
Only autowsgr/server/task_manager.py and its focused tests are changed. This PR does not alter scheduler behavior, decisive error mapping, response schemas, native types, or device leasing.