They should either complete successfully (i.e. because we concluded "yes, still conflicted") or just not start in the first place (i.e. because we know it's already conflicted, so why download a Snapshot at all).
Beware that care may be required here: a file may become conflicted with Participant A and then some time later also become conflicted with Participant B -- we still want to detect that second case (while still under conflict to A). That is, we shouldn't download any additional updates for "A" after detecting the conflict, but we probably do want to download updates from other participants (so we can record more conflicting participants, if they do indeed conflict).
According to https://whetstone.private.storage/privatestorage/privatestoragedesktop/-/issues/791#note_30691 it appears that conflicted files are queued for download, but never complete.
They should either complete successfully (i.e. because we concluded "yes, still conflicted") or just not start in the first place (i.e. because we know it's already conflicted, so why download a Snapshot at all).
Beware that care may be required here: a file may become conflicted with Participant A and then some time later also become conflicted with Participant B -- we still want to detect that second case (while still under conflict to A). That is, we shouldn't download any additional updates for "A" after detecting the conflict, but we probably do want to download updates from other participants (so we can record more conflicting participants, if they do indeed conflict).