You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In TestCommandInteraction::TestCommandHandlerWithProcessReceivedEmptyDataMsg, the act of sending an invoke where messageIsTimed did not match transactionIsTimed previously used to result in a status response being sent out.
I don't see that anymore after I synced up to master
The text was updated successfully, but these errors were encountered:
In a normal message reception flow it would be sent (by the caller). TestCommandHandlerWithProcessReceivedEmptyDataMsg directly calls an internal implementation function that returns status that the caller then sends. Perhaps it should check the returned status?
Ah ok. In that case, will take off the spec label.
mrjerryjohns
changed the title
Status Response not being sent when isTimed flag is set incorrectly
TestCommandHandlerWithProcessReceivedEmptyDataMsg not quite checking the status returned from ProcessInvokeRequestAug 12, 2022
Problem
In
TestCommandInteraction::TestCommandHandlerWithProcessReceivedEmptyDataMsg
, the act of sending an invoke where messageIsTimed did not match transactionIsTimed previously used to result in a status response being sent out.I don't see that anymore after I synced up to master
The text was updated successfully, but these errors were encountered: