Internal plumbing lets concurrent writers update shared state without clobbering each other.
A compare-and-swap retry helper and a namespace classifier exist, marking task, team and identity data as versioned; nothing user-facing calls it.
What's wrong with this entry?
An internal helper read-modify-writes a storage key with ifMatch/ifAbsent preconditions and retries with backoff when the precondition fails, so concurrent writers do not clobber each other.
- retries on
PreconditionFailedandAlreadyExistswith backoff - refuses keys whose namespace is classified 'plain' (last-writer-wins) and returns an
InvalidArgumenterror naming the offending argument - a new namespace-discipline classifier marks
task,team,identityand plainglobalConfigas versioned; settings, memory, cache, state, job and userConfigDir are plain
casRetry arbitrates versioned keys only
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.227
A new storage backend is being wired through the whole CLI
Both mention storage backend
-
v2.1.227
A new storage backend is wired through nearly everything, but never built
Both mention storage backend
-
v2.1.227
A new storage backend is wired through the product but returns nothing
Both mention storage backend