Skip to content
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

Raise exception on failure rather than SIGPIPE signal #31

Merged
merged 3 commits into from
Sep 10, 2016

Conversation

matthill
Copy link
Contributor

@matthill matthill commented Sep 8, 2016

PR for issue #30

Doing this allows us to gracefully attempt a reconnection.  Otherwise, we'll never know (since false can be returned both in the case of message failure and in the case where no message is returned)
@matthill matthill changed the title Mhill Raise exception on failure rather than SIGPIPE signal Sep 8, 2016
@deepfryed
Copy link
Owner

@matthill could you rename BeanstalkConnectException to ConnectException ?

@deepfryed
Copy link
Owner

Looks good otherwise.

@deepfryed
Copy link
Owner

It's late in the night here, I'll have a look tomorrow morning and merge. 💤

@matthill
Copy link
Contributor Author

matthill commented Sep 8, 2016

OK. This is done. FYI, I didn't throw exceptions for all the C++ wrappers (e.g., put, peek, list_tubes, etc). Not because we shouldn't, just laziness I suppose.

@deepfryed deepfryed merged commit 96d05c0 into deepfryed:master Sep 10, 2016
@deepfryed
Copy link
Owner

thanks @matthill 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants