Not switched on
Useful2 Signal3
The jobs view can offer dispatch-and-open for some local setups.
Requires the local backend plus a second condition that is not legible.
What's wrong with this entry?
Anonymous. No account, no email.
What
The job list's hint area now receives a dispatch-and-open capability, true only when the selected backend is "local" and a further condition holds. What that second condition tests is not legible in this build, so which local setups get it is undetermined.
Evidence
canDispatchAndOpen
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
Background job state and roster writes can route through the v5 storage backend
Both mention background
-
v2.1.223
Telemetry for transient background-job state read failures
Both mention background
-
v2.1.223
Roster orphan adoption reports itself
Both mention background