{"push_id":665168291,"size":2,"distinct_size":2,"ref":"refs/heads/RB15.04","head":"b4958ef2405f438121c11f5b7c055f206bb1e9d9","before":"3815660e0e0eba942962cdc723f12f1c6aa437b2","commits":[{"sha":"7df7c98749ac46b93e9fae2a263deeff6e625e48","author":{"email":"df8dfa71040b8f1d9001b78aa2f921797b5eb662@microsoft.com","name":"Rob Smith"},"message":"ASACORE-1978: AllJoyn returns incorrect error if named pipe transport fails\n\nIf a developer doesn't include the allJoyn capability in their app manifest\nthen connecting to the named pipe will fail with ERROR_ACCESS_DENIED.\nHowever, this error ends up being overwritten by the status returned from\nthe bundled router transport, so the developer has no idea why the\nconnection failed.\n\nWe need to change the transport to return a better error than it currently\ndoes, and modify the BusAttachment code to return the error for the\nrequested connection if connections are unsuccessful, instead of the error\nfrom the bundled router attempt.\n\nChange-Id: Ib9a08215b8367f85705312d23fbce73b82c35dc6\nSigned-off-by: Rob Smith <robs@microsoft.com>","distinct":true,"url":"https://api.github.com/repos/allseenalliance/core-alljoyn/commits/7df7c98749ac46b93e9fae2a263deeff6e625e48"},{"sha":"b4958ef2405f438121c11f5b7c055f206bb1e9d9","author":{"email":"e8f78e5b7f6be5b414ddc80db4e252c7fce2e346@qce.qualcomm.com","name":"Todd Malsbary"},"message":"Merge \"ASACORE-1978: AllJoyn returns incorrect error if named pipe transport fails\" into RB15.04","distinct":true,"url":"https://api.github.com/repos/allseenalliance/core-alljoyn/commits/b4958ef2405f438121c11f5b7c055f206bb1e9d9"}]}