Document use of retry_on_error for dedicated inference endpoints
#554
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Shortly after huggingface#549, the inference endpoint backend was updated to block by default on model loading. This PR adds documentation explaining how to circumvent that blocking so that the user, if desired, can handle the 500 errors themselves.
|
CC: @coyotte508 |
|
Thank you! Just a note, the backend hasn't been updated yet but should be in the coming days. (And waiting for endpoints to be scaled actually needs #555, my bad) |
coyotte508
approved these changes
Mar 14, 2024
Makes sense, thanks for the heads up 👍
Will defer to you folks on when is best to merge this PR in. |
|
Backend was updated, and version |
|
Amazing (: will give it a try soon-ish and report back. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Shortly after #549, the inference endpoint backend
was updated to block by default on model loading.
This PR adds documentation explaining how to
circumvent that blocking so that the user, if
desired, can handle the 500 errors themselves.