Title: Retry on connection timeout by andrefurlan-db · Pull Request #103 · databricks/databricks-sql-python · GitHub
Open Graph Title: Retry on connection timeout by andrefurlan-db · Pull Request #103 · databricks/databricks-sql-python
X Title: Retry on connection timeout by andrefurlan-db · Pull Request #103 · databricks/databricks-sql-python
Description: A lot of the time we see the error [Errno 110] Connection timed out. This happens a lot in Azure, particularly. In this PR I make it a retryable error as it is safe
Open Graph Description: A lot of the time we see the error [Errno 110] Connection timed out. This happens a lot in Azure, particularly. In this PR I make it a retryable error as it is safe
X Description: A lot of the time we see the error [Errno 110] Connection timed out. This happens a lot in Azure, particularly. In this PR I make it a retryable error as it is safe
Opengraph URL: https://github.com/databricks/databricks-sql-python/pull/103
X: @github
Domain: github.com
| route-pattern | /_view_fragments/voltron/pull_requests/show/:user_id/:repository/:id/pull_request_layout(.:format) |
| route-controller | voltron_pull_requests_fragments |
| route-action | pull_request_layout |
| fetch-nonce | v2:ec578772-b07b-1534-942d-5d4423e4afb4 |
| current-catalog-service-hash | ae870bc5e265a340912cde392f23dad3671a0a881730ffdadd82f2f57d81641b |
| request-id | ED0C:2E35ED:57BA58:749869:69715B34 |
| html-safe-nonce | 5f3c3b6ba9824028f5b2fdb4e8ed87e3088d809e335fa66c3daa561c41345fd6 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFRDBDOjJFMzVFRDo1N0JBNTg6NzQ5ODY5OjY5NzE1QjM0IiwidmlzaXRvcl9pZCI6IjM2NDc0NDkxOTc3NzEzMTYwMjAiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 739a84bb720a7e5ff104f80c1cba7f7e08bbd71e66e34e4d56fb6efa724817c4 |
| hovercard-subject-tag | pull_request:1312947247 |
| github-keyboard-shortcuts | repository,pull-request-list,pull-request-conversation,pull-request-files-changed,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/voltron/pull_requests/show/databricks/databricks-sql-python/103/pull_request_layout |
| twitter:image | https://avatars.githubusercontent.com/u/4998052?s=400&v=4 |
| twitter:card | summary |
| og:image | https://avatars.githubusercontent.com/u/4998052?s=400&v=4 |
| og:image:alt | A lot of the time we see the error [Errno 110] Connection timed out. This happens a lot in Azure, particularly. In this PR I make it a retryable error as it is safe |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | andrefurlan-db |
| hostname | github.com |
| expected-hostname | github.com |
| None | 1c338feb2465fb28789c852d4d9bbb3a30c0620671d1df7914edfbde84531d5e |
| turbo-cache-control | no-preview |
| go-import | github.com/databricks/databricks-sql-python git https://github.com/databricks/databricks-sql-python.git |
| octolytics-dimension-user_id | 4998052 |
| octolytics-dimension-user_login | databricks |
| octolytics-dimension-repository_id | 493695132 |
| octolytics-dimension-repository_nwo | databricks/databricks-sql-python |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 493695132 |
| octolytics-dimension-repository_network_root_nwo | databricks/databricks-sql-python |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | ca28321bb5dd58db88720c48080666bfbe28520a |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width