Is there a way to handle errors if client fails to connect to remote?

[peteclark82]

Hi,

I'm sure i must be missing something, but I can't find a way to determine if the client fails to connect to the remote. I thought the init method would be a good candidate for receiving the error, but it doesn't seem to invoke the callback, it just logs an error to the console.

What do I need to register a callback with to handle this event?

Cheers
Pete

[danjenkins]

Hi,

I don't think you're missing anything, in fact I think there's an
awful lot more that can be done, I happened to have exactly the same
issue today. There's a status command that I don't think we're
currently using and we should be able to give a better callback on
init too.

I'm in the middle of refactoring all of the project to deal with
errors better so this should be done at the same time,

I hope this at least helps in the fact that you're not missing
anything, as far as I'm aware at least

Dan

On Jul 6, 2012, at 18:31, Pete Clark
reply@reply.github.com
wrote:

Hi,

I'm sure i must be missing something, but I can't find a way to determine if the client fails to connect to the remote. I thought the init method would be a good candidate for receiving the error, but it doesn't seem to invoke the callback, it just logs an error to the console.

What do I need to register a callback with to handle this event?

Cheers
Pete

---

Reply to this email directly or view it on GitHub:
#32

[peteclark82]

Hi Dan,

Thanks for the reply. Yeah that clarification has put my
mind to rest, so I can implement a work around for the interim. I Just didn't want to hack anything purely through a lack of understanding.