-
Notifications
You must be signed in to change notification settings - Fork 894
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catch error on startup #75
Comments
Ok so I'm pretty sure it happens here: |
This fixes it:
|
@randomandy HI Andy. Thanks for catching this bug! I'm quite busy at the moment so it might take me few days to take a look. If you want, create a PR with a fix and I will try to look at it and merge it this weekend if time allows. |
@RichardKnop Hey Richard. Sure thing, happy to help. Fix is in #76 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So I have something like this:
which leads to this if the worker cannot connect to the broker on startup:
I'm trying to figure out where the process dies.
server.RegisterTasks(tasks)
or inworker = server.NewWorker("machinery_worker")
(I'm catching all other errors).Although the output would suggest that the error actually occurs during
worker.Launch()
, which leads me to believe that there's a bug in the error handling (because err comes back asnil
)?The text was updated successfully, but these errors were encountered: