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

Running "pub get" on pubspec.yaml changes during a Git branch change is too agressive #1651

Closed
DanTup opened this issue Apr 26, 2019 · 0 comments · Fixed by #1658
Closed
Labels
in commands Relates to commands (usually invoked from the command Palette) is bug
Milestone

Comments

@DanTup
Copy link
Member

DanTup commented Apr 26, 2019

Doing this with Flutter repo open for ex. results in tons of concurrent runs (normally we would do them sequentially when opening a project with multiple out of date, but I think we also special-case Flutter repo).

@DanTup DanTup added is bug in commands Relates to commands (usually invoked from the command Palette) labels Apr 26, 2019
@DanTup DanTup added this to the v2.26.1 milestone Apr 26, 2019
DanTup added a commit that referenced this issue Apr 29, 2019
Previously we could simultaneously fire off many, but pub doesn't handle concurrent fetches very well. This will run it automatically for one change, but show the "Some packages are out of date" prompt for > 1.

Fixes #1651.
DanTup added a commit that referenced this issue Apr 29, 2019
Previously we could simultaneously fire off many, but pub doesn't handle concurrent fetches very well. This will run it automatically for one change, but show the "Some packages are out of date" prompt for > 1.

Fixes #1651.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in commands Relates to commands (usually invoked from the command Palette) is bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant