Remote control config can be read through the storage backend, with clearer failure reasons.
An alternative storage-backed read path for remote control config exists, with no code deciding which path runs.
What's wrong with this entry?
Reading the remote control configuration gained an alternative path that goes through a storage backend rather than reading the file directly, classifying the result as text, absent, refused, failed or thrown. Absent maps to an empty config, and failures produce distinct messages that include the backend's error code. Which path a given session takes is not decided anywhere in this build.
failed to read
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
Compare-and-swap retry helper for versioned storage keys
Both mention storage backend
-
v2.1.223
Daemon lock and auto-update lock gained storage-backend implementations
Both mention storage backend
-
v2.1.223
Deep-link registration and cleanup sentinels can be stored as state keys
Both mention storage backend