- Notifications
You must be signed in to change notification settings - Fork250
PermalinkChoose a base ref {{ refName }}default Choose a head ref {{ refName }}default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also orlearn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also.Learn more about diff comparisons here.
base repository:replicate/replicate-python
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
Uh oh!
There was an error while loading.Please reload this page.
base:1.0.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
...
head repository:replicate/replicate-python
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
Uh oh!
There was an error while loading.Please reload this page.
compare:1.0.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
- 2commits
- 4files changed
- 1contributor
Commits on Oct 16, 2024
Configure read timeout based on
wait
parameter (#373)This fixes a bug in the new `wait` implementation where the default readtimeout for the HTTP client is shorter than the timeout on the server.This results in the client erroring before the server has had theopportunity to respond with a partial prediction.This commit now provides a custom timeout for the `predictions.create`request based on the `wait` parameter provided. We add a 500ms buffer tothe timeout to account for some discrepancy between server and clienttimings.I attempted to try and refactor the shared code between models,deployments & predictions but gave up. We now have a single functionthat creates the `headers` and `timeout` params and passes them in atthe various call sites.
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:git diff 1.0.1...1.0.2
Uh oh!
There was an error while loading.Please reload this page.