Remote file creates can refuse to overwrite an existing file and both calls accept cancellation.
A not_exists precondition exists on remote create, with no caller in this build requesting it.
What's wrong with this entry?
The remote file store's create call takes an options argument that can attach a not_exists precondition, so a create fails rather than overwriting, and both create and update now accept an abort signal. Nothing observed in this build requests the precondition, so whether any caller uses it is not settled here.
"not_exists"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Telemetry event for org-memory connected mode
Both mention store
-
v2.1.239
File uploads report why they failed and stop retrying forever
Both mention file
-
v2.1.239
Directory sync tracks content-filtered files, skip-worktree paths and named-backend reads
Both mention file