A bridge answering a cloud session's hooks on your machine is built behind an unresolved condition.
The forwarded-hook bridge is constructed at one site that returns nothing unless a second, undecided condition holds.
What's wrong with this entry?
A new component wires a cloud session's hooks back to your machine, so hook callbacks raised remotely can be answered and released locally. It is constructed at exactly one place, and that place returns nothing unless the session is not view-only and a second condition holds.
- The bridge registers callbacks for a forwarded hook firing and for one being cancelled, backed by the session manager's respond and release operations, and re-registers on stream connect, worker init, settings change and consent.
- The condition at the call site is a bare function call. The only declaration of that name in the file returns false unconditionally, but this bundle reuses the same short names for different functions across chunks, so the file alone does not establish which one is in scope there.
onForwardedHookCallback
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