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

HotFix for SetTimeout() having no effect #179

Closed
wants to merge 1 commit into from

Conversation

dhymik
Copy link
Contributor

@dhymik dhymik commented Jan 2, 2024

This fixes #127 ("A customer reported that it's not possible to set the HTTP Timeout at all now.")

See this comment for the idea to this pull request.

Problem:
deepgram.SetHttpClientTimeout(...) has no effect.

Hotfix:
removed .HttpClient.Create() in HttpClientUtil.SetTimeOut(TimeSpan timeSpan)

removed .HttpClient.Create() in HttpCLientUtil.SetTimeOut(TimeSpan timeSpan)
@bmaluijb
Copy link

Please get this released ASAP. This bug is costing me money

@dvonthenen
Copy link
Contributor

As I mentioned here:
https://github.com/orgs/deepgram/discussions/554

I am just coming on board to the project and will be taking a look at this today along with other .NET related stuff. From a quick glance, it looks like it isn't much of a fix but more trying to undo a mistake. We need to verify and perform due diligence before committing any changes to prevent any unintended consequences of the change. If you rollback to .NET v3.1.0 that should remove the timeout functionality and get you going again.

@dvonthenen
Copy link
Contributor

This PR #207 has been merged and released 3.4.1.

@dvonthenen dvonthenen closed this Feb 6, 2024
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.

A customer reported that it's not possible to set the HTTP Timeout at all now.
3 participants