Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

The read_timeout should default to nothing instead of 60 seconds #814

Closed
rzvoncek opened this issue Oct 9, 2024 · 0 comments · Fixed by #813
Closed

The read_timeout should default to nothing instead of 60 seconds #814

rzvoncek opened this issue Oct 9, 2024 · 0 comments · Fixed by #813

Comments

@rzvoncek
Copy link
Contributor

rzvoncek commented Oct 9, 2024 •
edited by sync-by-unito bot
Loading

Project board link

As we got notified here, the way we introduced the read_timeout setting is not too compatible with existing instalations. The 60 seconds timeout is not good enough for everybody.

We should default to no timeout, and only pass it in if it's actually configured.

┆Issue is synchronized with this Jira Story by Unito
┆Reviewer: Alexander Dejanovski
┆Issue Number: MED-100
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

MED-100 Make read_timeout default to None, only use it if set thelastpickle/cassandra-medusa
1 participant
@rzvoncek