[basex-talk] ~webdav locks + server stop = conflicted locks

This Issue occurs when the server stops while files are open/locked:

When basex starts it doesn't show lock icons on files the user had locked before the server stopped.

When users tries to open a file oxygen says the file is locked, even though the current user owns the lock. In other words, the lock seems to be tracking something that doesn't survive sessions.

To recover, we delete the webdav db + restart Oxygen.

Granted, doing all check-ins prior to stopping the server for maintenance would be a best practice. But in case of an unexpected failure, since the lock are saved in ~webdav, is there anyway we could get back to the locks as set in ~webdav?