{"push_id":608890149,"size":2,"distinct_size":1,"ref":"refs/heads/zombie","head":"4bc4efec60b2f516cb006378428b88f465b6b5b8","before":"3a5502904b2c328a9d4758d3ba33635c9c53bb7c","commits":[{"sha":"a2aa1fee4e7ff8a49a929a4e7bbca996c5631832","author":{"email":"7ad84288e3519c592b4e7cb171a021fa314ab03c@microsoft.com","name":"Xiaohongt"},"message":"change the testhost port","distinct":false,"url":"https://api.github.com/repos/aspnet/SignalR-Client-Cpp/commits/a2aa1fee4e7ff8a49a929a4e7bbca996c5631832"},{"sha":"4bc4efec60b2f516cb006378428b88f465b6b5b8","author":{"email":"e4d46f503d8f9cedce65b9393b52c237bee5bd40@gmail.com","name":"Pawel Kadluczka"},"message":"GhostsFromThePastLife - fixing a bug where stray errors caused reconnects\n\nWhen we stop a connection we just signal that the transport should be stopped but don't wait for it to actually stop. If then the same connection is immediately started the old transport can still be running. Because the callbacks are not reset when stopping the transport errors and messages from the old transport can still invoke them on the newly started connection. This is especially harmful in case of errors because they would cause reconnects. The fix is to ignore any message or error received from a transport started by a connection that has already been stopped.","distinct":true,"url":"https://api.github.com/repos/aspnet/SignalR-Client-Cpp/commits/4bc4efec60b2f516cb006378428b88f465b6b5b8"}]}