You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way the code is currently written, a sync is only marked as succeeded once it succeeds fully. Given that we progress package by package, we should be able to save checkpoint intermediate progress if the program crashes for some reason.
An alternative implementation that worked for me locally in such a scenario was:
and changing the sync functions to accept packages and to not dig into the diff map contents anymore. Would you be interested in such a change?
Additionally, in the delete part, the code in master is currently calling Map.delete/2 with a list instead of Map.drop/2 with the list of names to drop which is a bug.
That list is likely to be much smaller, but could be given the same treatment as create/update for consistency:
The way the code is currently written, a sync is only marked as succeeded once it succeeds fully. Given that we progress package by package, we should be able to save checkpoint intermediate progress if the program crashes for some reason.
An alternative implementation that worked for me locally in such a scenario was:
and changing the
sync
functions to acceptpackages
and to not dig into thediff
map contents anymore. Would you be interested in such a change?Additionally, in the
delete
part, the code in master is currently callingMap.delete/2
with a list instead ofMap.drop/2
with the list of names to drop which is a bug.That list is likely to be much smaller, but could be given the same treatment as create/update for consistency:
The text was updated successfully, but these errors were encountered: