Concurrency issue in sync

[vinayvenu]

Scenario

When an encounter sync takes a long time, there could be individuals and encounters created, causing sync errors. We should always have a single endDate(now) for the entire duration of the sync.

Acceptance criteria

• The nowMinus10Seconds returned by the /syncDetails call is used as the now parameter in all sync fetch calls

[mahalakshme]

@vinayvenu let me know the details that APF reported - it might not be a concurrency issue also - did they they any user name etc.,

[vinayvenu]

This is working as designed. Verified client calls, added test in server to ensure this does not happen. adb logs attached

sync_log.txt

grep "prerelease.avniproject.org" adb_log.txt | grep GET | cut -f7 -d' ' | cut -f4 -d'=' | cut -f1 -d'&' | uniq

[mahalakshme]

@AchalaBelokar to test: when an entry, say encounter is created when sync is happening, the encounter should not get synced to the mobile device.

@vinayvenu I think we can add this in readme as sync behavior, will help implementors when debugging. may be here: https://avni.readme.io/docs/internal-details-of-avni-sync#other-tidbits - currently it tells data in the server for more than 10 secs which is not right since it is "start of the sync time" - 10secs right?

[vinayvenu]

Done