vorotamoroz

Thank you for finding the edge case. I have a bad feeling about this. We have to investigate it more, but in renaming, saving the new file is prior to...

@Vyeche Sorry for being late. It has been fixed in case-sensitive platforms. (Unfortunately, Windows does not respect cases. But it would not be a `Parse error` again.)

Sorry for this, The expression was too much as it came to mind. My laziness. This means > We keep the deleted document for history and diff, but it could...

This message can be ignored. Just history has been detected. (But I have begun to think this message should be shown as a verbose one...) History of deleted metadata can...

`Delete metadata of deleted files` will remove metadata on deletion. But if the conflict occurs again after synchronisation, it will be detected (CouchDB is amazing). Even if we have dismissed...

Thank you for asking me! looks like so you are troubled. Does every synchronising raise this error? or can sometimes be done? And could you please check the response that...

Thank you for the detail! But still, I am wondering what makes this. I'm very glad you have helps. We can reduce the batch size at `Batch size` and `Batch...

Thank you! It may have happened with the chunk sizes. If we had changed the chunk size, these are effects only subsequent changesets. > Next, the check database log did...

Thank you for the file! I tried synchronising the file and synchronising could be done straightly, Maybe this can be sent normally with our latest configuration.

Hi! Thank you for your opinion! What sort of SDK do you need? For now, common utilities and functions are extracted into [subrepos](https://github.com/vrtmrz/livesync-commonlib). Or plugin-to-plugin interop? If you have any...