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

Propagate exceptions from connect() #41

Merged
merged 1 commit into from
Feb 11, 2024
Merged

Conversation

srd424
Copy link
Contributor

@srd424 srd424 commented Feb 9, 2024

Move try/except from connectBroker to runConnect, so vanilla connect() will throw an exception on error. We change the initial state for new contexts to Disconnected to simplify the logic in runConnect() slightly.

Alternative to #40, closes #39.

will throw an exception on error. We change the initial state for
new contexts to Disconnected to simplify the logic in runConnect()
slightly
@ThomasTJdev
Copy link
Collaborator

I prefer this over #40. It's a good improvement - thanks @srd424 !

@ThomasTJdev ThomasTJdev merged commit e48cb10 into zevv:master Feb 11, 2024
3 checks passed
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.

connect() does not raise exception on error
2 participants