-
Notifications
You must be signed in to change notification settings - Fork 876
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
background tasks should exit when summary/clone/compact/info killed. #4754
Labels
Comments
zhoucheng361
changed the title
background tasks should exit when summary/sync/warmup/ls killed.
background tasks should exit when summary/sync killed.
Apr 24, 2024
zhoucheng361
changed the title
background tasks should exit when summary/sync killed.
background tasks should exit when summary/sync/clone killed.
Apr 24, 2024
zhoucheng361
changed the title
background tasks should exit when summary/sync/clone killed.
background tasks should exit when summary/clone killed.
Apr 24, 2024
zhoucheng361
changed the title
background tasks should exit when summary/clone killed.
background tasks should exit when summary/clone/compact killed.
Apr 24, 2024
zhoucheng361
changed the title
background tasks should exit when summary/clone/compact killed.
background tasks should exit when summary/clone/compact/info killed.
Apr 24, 2024
zhoucheng361
added
kind/enhancement
and removed
kind/feature
New feature or request
labels
Apr 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added:
when user interrupted summary/clone by Ctrl+C, the corresponded tasks run in the mount process should exit.
Why is this needed:
otherwise the memory will increase to a large amount until the task finish.
The text was updated successfully, but these errors were encountered: