You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
We want to limit the amount of time we spend on attempting to fetch data for any one image repo, in the interest of fairness. Currently the operation uses a client, created by a factory, which gets a context with a deadline. But it is a better use of context.Context to supply the context to the operation, so the caller has the choice of deadline, timeout, or whatever.
The text was updated successfully, but these errors were encountered:
philwinder
changed the title
Use context.WithDeadline() for limiting repo fetches
Make image fetch deadline user configurable and use deadline, not timeout
Aug 24, 2017
- Use WithDeadline rather than WithTimeout
- Make deadline configurable
Fixes#713
squaremo
changed the title
Make image fetch deadline user configurable and use deadline, not timeout
Supply context to image fetch operation
Aug 24, 2017
We want to limit the amount of time we spend on attempting to fetch data for any one image repo, in the interest of fairness. Currently the operation uses a client, created by a factory, which gets a context with a deadline. But it is a better use of
context.Context
to supply the context to the operation, so the caller has the choice of deadline, timeout, or whatever.The text was updated successfully, but these errors were encountered: