Closed MBakerParagon closed 3 years ago
Signed-off-by: MBakerParagon mbaker@paragoninnovations.com
d91de45 accidentally got rid of the fix from 7aa44d9.
More info here.
7aa44d9
The current state of both develop and master are back to the bug described in the link above. I just tested it and this fixes that behavior.
Before:
client wakes -> has a waiting message -> sends a pingreq -> the gateway responds with the waiting message
Now:
client wakes -> has a waiting message -> sends a pingreq -> the gateway responds with the waiting message ->gateway sends pingresp
Looks like my second attempt should pass all checks. I have no idea why I was having so much trouble with the sign off.
Signed-off-by: MBakerParagon mbaker@paragoninnovations.com
d91de45 accidentally got rid of the fix from 7aa44d9.
More info here.
7aa44d9
The current state of both develop and master are back to the bug described in the link above. I just tested it and this fixes that behavior.
Before:
client wakes -> has a waiting message -> sends a pingreq -> the gateway responds with the waiting message
Now:
client wakes -> has a waiting message -> sends a pingreq -> the gateway responds with the waiting message ->gateway sends pingresp