Commands which share the same reply might get Handler Stuck #547
As happened with the PAMCAM Handler of Flying Laptop:
- There are two Commands in a DH which use the same Reply
- The first command was sent
- Before the reply was received or a timeout happened the other command was sent
- The first command will be stuck forever as the Reply Map was set to the other command.
The implementation had to overwrite
enableReplyInReplyMap to call the default DHB implementation with
"useAlternativeId = True". The DHB function does not check if the reply is currently in use.
Implementations can solve this by checking that a command with the same reply is executing before commanding. I think, that the DHB function
enableReplyInReplyMap should not overwrite
info->command = command; if
isExecuting is True.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?