exit 5 instead of raising error if no etcd endpoint responds

[viktorerlingsson]

WHAT is this pull request doing?

Exit 5 (5th letter, E, for etcd) instead of raising error when no etcd endpoint responds.

fixes #872

HOW can this pull request be tested?

Try starting LavinMQ with clustering enabled and no etcd running.

[carlhoerberg]

I did this for exit 3: 5fd0ea0 So it won't exit specs.. it's not pretty though :/

[viktorerlingsson]

I did this for exit 3: 5fd0ea0 So it won't exit specs.. it's not pretty though :/

Did the same here for now 👍

IMO let's go with that solution until we figure out something better!

[carlhoerberg]

I reverted that, exiting in code, if the code is running in a fiber nothing would rescue and exit it.

[carlhoerberg]

Check if we can override abort in specs

[viktorerlingsson]

Check if we can override abort in specs

Yes we can, just something like the following in spec_helper works. But we should probably raise an exception that we can catch in the specs where we want LavinMQ to exit.

def abort(reason = "")
end

[spuun]

Yes we can, just something like the following in spec_helper works. But we should probably raise an exception that we can catch in the specs where we want LavinMQ to exit.

So we can just do:

def abort(reason = "")
raise reason
end

But maybe it's worth defining a SpecExitError or something.