You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment if you stop a kit import command in progress, the temporary files don't get automatically deleted. There should be an indicator for users to delete the temporary file being created.
The text was updated successfully, but these errors were encountered:
Currently, kit does not try to handle signals (pressing ctrl+c will sent SIGINT to the process), so when it encounters the signal it exits immediately. This prevents both doing any cleanup of files locally, but also printing any messages suggesting you should clean up manually.
We can catch and ignore signals, but I'm not sure it's a standard thing to do -- it could be annoying to have kit not exit immediately on SIGINT.
For what it's worth, we use temporary directories on all OSes for this process, so those files would be automatically deleted on restart.
bmicklea
changed the title
At the moment if you stop a kit import command in progress, the temporary files don't get automatically deleted. There should be an indicator for users to delete the temporary file being created.
Stopping kit import doesn't clear temporary files
Feb 3, 2025
Closing this as won't fix since the solution to fix it is potentially more cumbersome and annoying for users than the current situation. Because these files get cleaned up on restart the severity of the issue isn't very high.
At the moment if you stop a kit import command in progress, the temporary files don't get automatically deleted. There should be an indicator for users to delete the temporary file being created.
The text was updated successfully, but these errors were encountered: