Conversation
|
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.
A manual backup started from the Create Backup screen could not be stopped. The screen showed "Please wait" until the backup finished, and for a live world the runtime handed the screen a result stage that ignored cancel.
The operation screen now shows a Cancel button while a backup creation runs. Cancel stops the running stage. For a live world the runtime returns a result view whose cancel goes through the same handler as the world-exit toast: it interrupts the capture thread while the world is copied, and cancels the coordinator operation once dispatched. The coordinator already removes the private capture and the partial ZIP, interrupts the Git write and cleans its staging, and keeps a destination that had finished before the stop. The screen reports "Backup cancelled" instead of a failure and offers no retry.
The cancellation check moved into
AsyncTasksso the toast and the screen share one definition; a unit test covers it. The runtime and screen changes need the Minecraft client, so they were verified by build only.Made with Claude Fable 5.1 in Claude Code.
🤖 Generated with Claude Code