{"push_id":880040463,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"1608da2089e092ab20e0c6470655974b95861082","before":"4b622c86366922c7e8ed0361ecc9eb6281a416f5","commits":[{"sha":"d5f8af51f6935d32a37d6e14373ad710537c21d4","author":{"email":"044a2f5446224495d6813d561c55539f695c57ce@2ndQuadrant.com","name":"Abhijit Menon-Sen"},"message":"Explicitly accept become_success in awaiting_prompt state\n\nIf we request escalation with a password, we start in expecting_prompt\nstate. If the escalation then succeeds without the password, i.e., the\nbecome_success response arrives, we must explicitly move into the next\nstate (awaiting_escalation, which immediately goes into ready_to_send),\nso that we no longer try to apply the timeout.\n\nOtherwise, if the results of the task don't arrive with become_success\n(dependent on the exact timing), we leak the success notification and\neventually timeout. But if the module response did arrive before the\ntimeout expired, the \"process has already exited\" test would do the\nright thing by accident (which is why it didn't fail more often).\n\nFixes #13289","distinct":true,"url":"https://api.github.com/repos/2ndQuadrant/ansible/commits/d5f8af51f6935d32a37d6e14373ad710537c21d4"},{"sha":"1608da2089e092ab20e0c6470655974b95861082","author":{"email":"044a2f5446224495d6813d561c55539f695c57ce@toroid.org","name":"Abhijit Menon-Sen"},"message":"Merge remote-tracking branch 'extern/ssh-escalation'","distinct":true,"url":"https://api.github.com/repos/2ndQuadrant/ansible/commits/1608da2089e092ab20e0c6470655974b95861082"}]}