Week 9 Lab: Anatomy of a Conflict Copy
Find a real conflict copy in your own storage and read it as evidence of a decision the service refused to make
Version 1.2 · Supersedes v1.1 · Status: CURRENT
- v1.1: Teaching staff reassigned, and the worked example's name updated to match.
- v1.0: Cleaned up sentence by sentence; nothing substantive changed.
19 April 2027
Before the session#
Search your own storage for conflict copies. The naming varies by service:
conflicted copy, (1), Conflict, a device name in parentheses, a date
appended. Search for a few patterns rather than one. Record the full
filename verbatim, including punctuation and spacing. The filename is the
service’s incident report, and it is the only report it filed.
In the session#
Read each filename for what it discloses: which device or account lost, and what the service used as the timestamp. Then open both versions and determine whether they actually differ. Some conflict copies are byte- identical to the file they were forked from: the service saw a conflict in its bookkeeping that didn’t exist in the content. Note those separately; they are a different finding from a real divergence.
Afterwards#
For any pair that genuinely differs, state the difference in one sentence, and say which version you would have kept. Then note how long the conflict copy had been sitting there before this exercise made you open it. That interval is the actual measure of what the service’s report was worth.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- one real conflict copy located, with its exact filename recorded verbatim
- what the filename discloses, which device or person, and when
- whether the two versions actually differ, and what the difference is
Teaching team
- Naledi Mokoena: convenor