Found two problems with the core consistency logic

[Tobias Bouschen]

Hi all,

While working on enabling participants to create/delete/move/rename
shared files in Saros/I, I found two problems in the Saros Core
consistency logic. I already created bug-tracker entries for both of
them. Here is a short summary for both issues:


#223 Vector time does not get reset correctly when deleting a file
https://github.com/saros-project/saros/issues/223

When deleting and subsequently re-creating a file on the host's side,
the clients still uses the old vector time for the path. This leads to a
vector time mismatch between the host and the clients, resulting in
activities not being executed correctly.


#233 Saros sometimes creates ChecksumActivities for deleted/moved files
https://github.com/saros-project/saros/issues/233

When deleting/moving a file, the ConsistencyWatchdogServer on the host's
side sometimes creates ChecksumActivities before the deletion/move
activities were executed on the client side. If a client has an open
editor for the deleted/moved file, the host will still create a
ChecksumActivity for the old file path as it is still open in a remote
editor. This leads to an inconsistency being triggered on the client's
side as it thinks it is missing a file still present on the host's side.


The GitHub issues describe the problems in more details.

As I am still busy working on Saros/I, I currently don't have the time
to deal with this myself. If someone of you are interested and have the
time, I would appreciate if you could have a look at the linked issues.
If something is unclear, feel free to ask or make suggestions for
improvements.

Best regards,
Tobias