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
mmmarcos
changed the title
Add and manage the WorkspaceOpsOutboundSyncEntryConfined event
Manage confined entries in synchronization monitor
Aug 28, 2024
As mentioned in this conversation, the
WorkspaceOpsOutboundSyncEntryConfined
event has not been implemented.In parsec v2, it was emitted when a confined entry tries to get synchronized:
parsec-cloud/parsec/core/fs/workspacefs/sync_transactions.py
Lines 362 to 369 in d397c03
It was linked to a handler in the sync monitor:
parsec-cloud/parsec/core/sync_monitor.py
Lines 445 to 452 in d397c03
Which allowed the sync monitor to keep track of the confined entries and their respective cause.
This information was then used here:
parsec-cloud/parsec/core/sync_monitor.py
Lines 176 to 188 in d397c03
This way, all the confined entries corresponding to a given cause would get re-integrated into the synchronization system when the cause gets updated.
The text was updated successfully, but these errors were encountered: