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.

Sign up for GitHub

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

Jump to bottom

Improve Handling of WebSocketException errors for Self Hosted #339

Open
jpvajda opened this issue Sep 30, 2024 · 1 comment
Open

Improve Handling of WebSocketException errors for Self Hosted #339

jpvajda opened this issue Sep 30, 2024 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed low priority Do these last...
Milestone
.NET SDK Post-4.5

Comments

@jpvajda
Copy link
Contributor

jpvajda commented Sep 30, 2024

Users can set max_active_requests for for self-hosted deployments, (on-prem) as a configuration option in their TOML file.

When this is limit is hit they get a

WebSocketException with this message: "The server returned status code '429' limit exceeded, when status code '101' was expected."

We want to better surface a 429 status code so they can handle it on the server side using this SDK.
@jpvajda jpvajda added the enhancement New feature or request label Sep 30, 2024
@jpvajda
Copy link
Contributor Author

jpvajda commented Sep 30, 2024

@jkroll-deepgram / @dvonthenen 👋

@davidvonthenen davidvonthenen added help wanted Extra attention is needed low priority Do these last... labels Nov 7, 2024
@davidvonthenen davidvonthenen added this to the .NET SDK Post-4.5 milestone Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request help wanted Extra attention is needed low priority Do these last...
Projects
None yet
Milestone
.NET SDK Post-4.5
Development

No branches or pull requests
2 participants
@jpvajda @davidvonthenen