{"push_id":743381837,"size":1,"distinct_size":1,"ref":"refs/heads/remote-profiling","head":"5f110313d52635992dea57b7c0bf54d6b338dbd7","before":"1cb45252b8714310de0b99e90c4b320d11d157ef","commits":[{"sha":"5f110313d52635992dea57b7c0bf54d6b338dbd7","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@strongloop.com","name":"Ryan Graham"},"message":"executor: fix handling of generic requests\n\nThe callback given to a strong-control-channel request is only given a\nsingle argument: the response. Since the error, if any, is given as a\nproperty of that response we need to extract it to behave like a normal\nnode-back. Basically this wrapper wasn't doing what it was supposed to\nbe doing, but now it is.\n\nBandwidth usage aside, this seems to be the main thing that was\npreventing heap snapshots and cpu profiling from working.","distinct":true,"url":"https://api.github.com/repos/strongloop/strong-central/commits/5f110313d52635992dea57b7c0bf54d6b338dbd7"}]}