Provide user feedback on slow Gradle operations #11015
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mravn-google
force-pushed
the
gradle_feedback
branch
from
1ee6319 to
a6a8805
Compare
mravn-google
force-pushed
the
gradle_feedback
branch
from
a6a8805 to
48cd874
Compare
gspencergoog
pushed a commit
to gspencergoog/flutter
that referenced
this pull request
Jul 1, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bootstrapping Gradle via the Gradle Wrapper may involve downloading and unpacking a Gradle installation. Took 8 seconds last I tried.
Invoking Gradle afterwards (just to learn where it wants to put the apk) involves resolving dependencies, which may in turn involve downloading the internet. Took >30 seconds last I tried.
These processes are now executed by async functions and using a slow-op status logger to provide a reasonable UX.
Fixes #10994.