An unrecognized message no longer leaves your command hanging forever waiting for a result.
What's wrong with this entry?
An incoming message with an unrecognized type no longer leaves callers waiting on it forever.
- The handler extracts a
uuidif present and reports that command as "completed" through the lifecycle callback. - The existing "Ignoring unknown message type" warning is still emitted alongside.
Ignoring unknown message type:
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
The stdin transport now answers the remote-transport questions
Both mention transport
-
v2.1.248
Undelivered events can be handed to a replacement connection
Both mention transport
-
v2.1.248
Stalled WebSocket sends are now detected instead of hanging
Both mention transport