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

fix: catch correct exception type for connection problems #1600

Merged
merged 2 commits into from
Nov 16, 2023

Conversation

krille-chan
Copy link
Contributor

No description provided.

Copy link
Member

@nico-famedly nico-famedly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we not need the MatrixConnectionException then? Or is that also derived from IOException?

@krille-chan
Copy link
Contributor Author

Do we not need the MatrixConnectionException then? Or is that also derived from IOException?

No, this is only used in other requests which I also have changed in a PR in the matrix api lite. Sync should never throw an MatrixConnectionException

@nico-famedly
Copy link
Member

So we also don't need to depend on the newer api_lite, since it was already an IO error for this request?

@krille-chan
Copy link
Contributor Author

So we also don't need to depend on the newer api_lite, since it was already an IO error for this request?

Correct. It is for years already

@nico-famedly nico-famedly merged commit b06167b into main Nov 16, 2023
9 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.

3 participants