-
Notifications
You must be signed in to change notification settings - Fork 28.6k
Reland: Show output from pub get in flutter pub get #110851
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
Conversation
…ter#106300)" (flutter#110478)" This reverts commit 0e195e9.
The first commit is (hopefully) fixing the reason this was reverted. The process from @zanderso is there away to trigger the test that failed in #110478 ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Let me try to validate this test locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, flutter packages get is failing for me when I run this locally (not sure if I'm holding it wrong):
When I execute dart .\bin\test_runner.dart test -t windows_chrome_dev_mode
on this branch, I get:
[windows_chrome_dev_mode] [STDOUT] Executing "D:\git\flutter\bin\flutter packages get" in "C:\Users\chris\AppData\Local\Temp\edited_flutter_gallery" with environment {BOT: true, LANG: en_US.UTF-8}
[windows_chrome_dev_mode] [STDOUT] stdout: Running "flutter pub get" in edited_flutter_gallery...
[windows_chrome_dev_mode] [STDOUT] stdout: pub get failed (server unavailable) -- attempting retry 1 in 1 second...
[windows_chrome_dev_mode] [STDOUT] stdout: pub get failed (server unavailable) -- attempting retry 2 in 2 seconds...
[windows_chrome_dev_mode] [STDOUT] stdout: pub get failed (server unavailable) -- attempting retry 3 in 4 seconds...
[windows_chrome_dev_mode] [STDOUT] stdout: pub get failed (server unavailable) -- attempting retry 4 in 8 seconds...
[windows_chrome_dev_mode] [STDOUT] stdout: pub get failed (server unavailable) -- attempting retry 5 in 16 seconds...
[windows_chrome_dev_mode] [STDOUT] stdout: pub get failed (server unavailable) -- attempting retry 6 in 32 seconds...
Here's the documentation on running these locally: https://github.com/flutter/flutter/tree/master/dev/devicelab#running-specific-tests |
Hmm, I get through
|
Could you try running it once more? I don't think the message you saw "pub get failed (server unavailable)" can be related to this PR - it looks more like a network issue of sorts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this passes locally for you, I'll take your word for it (don't have my Windows machine today). This definitely seems like it fixed the issue the other PR got reverted for.
Reland of #106300 that was reverted here: #110478
Original description:
Part of dart-lang/pub#2971 .
dart pub get
has detailed output about outdated dependencies. This is currently not exposed fromflutter pub get
.We are missing out on at least this information:
Before:
Note how the warnings output really belongs to the resolution from the example.
After:
This PR also uses
pub get --example
(implemented here) to resolve in './example' if it exists.Now the output from resolution in ./example is reduced as long as there are no errors.
Because
flutter pub get
will retrypub get
until successful the output of each run is recorded, and only the output of the last run is shown.Fix: a small bug where
flutter create
for some templates would invoke pub even if given a--no-pub
argument.Cleanup:
pub get
will no longer be invoked with --no-precompile (that is now default).Output from
pub get
is also show when doingflutter create
- that might be distracting - maybe we should turn that off:Also includes color in the pub terminal output (depending on the flutter terminal color detection):
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.