A model switch over the control bridge replies immediately as pending, then follows up with the result.
What's wrong with this entry?
A model switch requested over the control bridge no longer has to resolve on the spot. If the verdict is still outstanding, the bridge replies at once that the switch is pending, waits up to 8 seconds, then sends a follow-up system notice saying the pending switch was applied or failed.
- The pending reply reads: "This model switch is still pending (an earlier model request or a PreModelSwitch hook has not finished); it will apply when that completes unless it is refused".
- The follow-up is "The pending model switch was applied" or "The pending model switch failed".
- The deadline can in principle be supplied per request, but nothing in the build sets it, so the built-in 8000ms default always applies.
- Typical causes of a pending verdict are an earlier model request still in flight or a PreModelSwitch hook that has not returned.
This model switch is still pending (an earlier model request or a PreModelSwitch hook has not finished); it will apply when that completes unless it is refused
Strings lifted out of the shipped bundle, so the claim above can be checked against them.