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

Catch ClientResponseError when checking running API #8426

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

qstokkink
Copy link
Contributor

Fixes #8415

This PR:

  • Fixes ClientResponseError not being caught in _is_url_available.

@qstokkink
Copy link
Contributor Author

validate

@qstokkink qstokkink changed the title WIP: Catch ClientResponseError when checking running API READY: Catch ClientResponseError when checking running API Jan 29, 2025
@qstokkink qstokkink marked this pull request as ready for review January 29, 2025 15:18
@qstokkink qstokkink changed the title READY: Catch ClientResponseError when checking running API Catch ClientResponseError when checking running API Jan 29, 2025
@qstokkink qstokkink merged commit 4b06f9c into Tribler:main Jan 29, 2025
7 checks passed
@qstokkink qstokkink deleted the fix_client_resp_error branch January 29, 2025 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

A ClientResponseError occurred
2 participants