Under the hood
Useful1 Signal1
Memory sync storage failures now raise named errors with a stable code and description.
What's wrong with this entry?
Anonymous. No account, no email.
What
Stat, read, write and delete of a local entry through storage in the memory sync paths now raise a named error with a formatted backend code and a stable description, instead of a bare error wrapping a cause.
Evidence
multi-store-sync: local entry not deletable via storage
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.