[Libreoffice-bugs] [Bug 113033] No error message when trying to save a locked document from a SMB external storage in Nextcloud with Collabora Online

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Fri Dec 7 09:22:21 UTC 2018


https://bugs.documentfoundation.org/show_bug.cgi?id=113033

Michael Meeks <michael.meeks at collabora.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|medium                      |low
           Severity|normal                      |enhancement
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #2 from Michael Meeks <michael.meeks at collabora.com> ---
First - Joel ! wonderful to see you again - hope all's well; would love to
catch up.

Second - distributed locking is a living hell. Even if making this rather
complex use-case possible was something we could do easily (and that's far from
clear - it's a mixed Nextcloud, Online issue) - we would then get a slew of
other bugs and use-cases around leaked lock-files; whether Nextcloud should try
to create lock files when it believes a document is open in Online (but only
when that is un-modified? rather than waiting for an hour to be expired?) etc.
- the area opens a enterprise-sized can of worms =)

Some of the reasons why I've resisted getting involved in distributed locking
at least ;-) and that's before we get into leaked locks, inconsistent locks
(where there is an OS/SMB lock on the file, but no lock-file or vv.) and so on
... anyhow.

It is possible we can improve this with some concerted effort; in theory WOPI
has locking extensions that can be implemented, but ... its a massive job to
get right, horribly hard to validate, and will inevitably be deeply
disappointing.

I'd prefer FWIW to work on more robust ways of visualizing and/or merging
changes ;-) now that is something generally useful & interesting.

Nevertheless - we should prolly keep this open, in the long run we may have to
do something here.

Philippe - how are you feeling about this ? and/or do you feel motiviated to
come up with a big matrix / description of the cases we need to handle
(including all the asynchronous races between each of those - it will be many
tens of different stats)  - and what we need to do in those cases.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20181207/d2792c72/attachment-0001.html>


More information about the Libreoffice-bugs mailing list