Skip to content

ImageStreamResolver can make multiple requests for the same image stream image #548

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

Closed
spadgett opened this issue Sep 19, 2016 · 5 comments
Assignees
Labels
area/performance kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P3

Comments

@spadgett
Copy link
Member

See #523 (comment)

@jwforres
Copy link
Member

The fix for this is low-level in data service. If we have a GET in flight we should keep a list of promises to resolve/reject once the GET finishes, similar to what we do with the callback lists for watch.

@spadgett
Copy link
Member Author

Lowering the severity since it will happen much less often now.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 8, 2020
@jwforres
Copy link
Member

/close

@openshift-ci-robot
Copy link

@jwforres: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/performance kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P3
Projects
None yet
Development

No branches or pull requests

4 participants