Skip to content
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

Show warning if no lock can be aquired #497

Open
hagenw opened this issue Feb 12, 2025 · 0 comments · May be fixed by #498
Open

Show warning if no lock can be aquired #497

hagenw opened this issue Feb 12, 2025 · 0 comments · May be fixed by #498
Labels
enhancement New feature or request

Comments

@hagenw
Copy link
Member

hagenw commented Feb 12, 2025

From time to time loading a dataset from a shared cache folder might get stuck for a long time (or for ever) as there is a leftover .lock file in the dataset. In some cases it might be valid, as another user started downloading the same dataset, but most often it happens due to leftover lock files, that couldn't be cleaned properly.

Thje biggest problem at the moment is that a user gets no feedback on what the problem is, and loading the data is simply stuck. We should try to avoid this by displaying that we are waiting to getting the lock to the folder and/or showing a warning message if the lock could not get acquired in 1 sec, that another user might be downloading the same data or that there is a leftover .lock file, which need to be manually deleted.

@hagenw hagenw added the enhancement New feature or request label Feb 12, 2025
@hagenw hagenw linked a pull request Feb 13, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant