You'll notice
Useful2 Signal3
A garbled reply from a paired device no longer ends the wait for the hook's real answer.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a hook runs on a paired device, a reply that is an error or that does not parse as a hook answer is now counted and logged instead of being accepted, and the session keeps waiting for the device's real answer.
Details
- Error text is truncated before it is written to the log.
Evidence
Ignoring malformed control_response for device hook_callback request_id=
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.234
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook
-
v2.1.236
Shutdown seals transcript writes and gives SessionEnd hooks more time
Both mention hook