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.

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

[Authentication] In authenticated multi-feed setup, PM-UI: Updates window hangs if one of the feeds is not authenticated #5033

Closed
anangaur opened this issue Apr 14, 2017 · 2 comments
Labels
Icebox cleanup candidate Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Product:VS.Client Status:Inactive Icebox issues not updated for a specific long time
Milestone

Comments

@anangaur
Copy link
Member

anangaur commented Apr 14, 2017

Repro steps:

  1. Have multiple feeds setup with atleast one authenticated feed
  2. Open PMUI, install a package that is present in atleast 2 feeds including the authenticated feed.
  3. Go to updates tab

Expected: It shows the update from the feed that is accessible.

Actual: It hangs, may be trying to connect to the authenticated feed. Even so many a times the login window is not shown so user is unaware of what's going on.

The update button on the package is also not shown - may be due to the same reason.

@anangaur anangaur changed the title [Authentication] In authenticated multi-feed env, PM-UI: Updates window hangs if one of the feeds is not authenticated [Authentication] In authenticated multi-feed setup, PM-UI: Updates window hangs if one of the feeds is not authenticated Apr 14, 2017
@mishra14 mishra14 added the Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. label Oct 17, 2017
@mishra14 mishra14 added this to the Backlog milestone Oct 17, 2017
@ghost ghost added the Status:Inactive Icebox issues not updated for a specific long time label Sep 1, 2022
@ghost
Copy link

ghost commented Nov 18, 2022

Due to lack of recent activity, this issue has been marked as a candidate for icebox cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will add a Triage:NeedsTriageDiscussion label and lead to a triaging process.
This process is part of the experimental Stale icebox issues cleanup we are currently trialing. Please share any feedback you might have in the linked issue.

@ghost
Copy link

ghost commented Dec 2, 2022

This issue will now be closed since it had been marked Icebox cleanup candidate, but received no further activity in the past 14 days.

@ghost ghost closed this as completed Dec 2, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Icebox cleanup candidate Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Product:VS.Client Status:Inactive Icebox issues not updated for a specific long time
Projects
None yet
Development

No branches or pull requests

4 participants