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.

Sign up for GitHub

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

Jump to bottom

Consider adding an "allow list" of SDK resolvers that can be used inside VS #4410

Closed
davkean opened this issue Dec 21, 2018 · 2 comments
Closed

Consider adding an "allow list" of SDK resolvers that can be used inside VS #4410

davkean opened this issue Dec 21, 2018 · 2 comments
Labels
Triage-Approved Reviewed and prioritized
Milestone
16.x

Comments

@davkean
Copy link
Member

davkean commented Dec 21, 2018

Rogue SDK resolvers can cause significant performance issues across the product, we should allow only a set of known "well-performing" resolvers to load inside VS to avoid VS being blamed for performance issues.
@jjmew jjmew added Feature Request Triage-Approved Reviewed and prioritized labels Jan 14, 2019
@jjmew jjmew added this to the 16.1 milestone Jan 14, 2019
@jjmew
Copy link
Contributor

jjmew commented Jan 14, 2019

The other way to think about this is to alert the user if a given SDK or SDK resolver is taking too long. We could use the traditional yellow bar.

@davkean davkean modified the milestones: 16.1, 16.X Jun 4, 2019
@davkean
Copy link
Member Author

davkean commented Dec 11, 2019

@jjmew That's exactly what I turned this into: #5732.

@davkean davkean closed this as completed Dec 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Triage-Approved Reviewed and prioritized
Projects
None yet
Milestone
16.x
Development

No branches or pull requests
3 participants
@drewnoakes @davkean @jjmew