-
Notifications
You must be signed in to change notification settings - Fork 29.1k
Update plugins dependencies for the Gallery test #69630
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
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat. Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
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.
Still LGTM
same issue :/ cc @dnfield - should we disable this test? |
@blasten is this the same branch? Or did you re-branch from a later commit? Only the former will change your flutter version |
New branch but with same commits from the previous one. Would that be the issue? |
I don't think so |
Could flutter_svg loosen the constraint a bit? @dnfield |
what about we don't block this PR on the |
We should be able to retag flutter SVG with a dev version that this won't fail on. I don't think I'll get to that before tomorrow but if anyone else does I can help land |
@mehmetf are we allowing null-safety plugins internally? I might need to do that shortly, see "Google testing". |
Will import the plugin into g3 in a bit. |
@blasten I think this has/will break the build. When I sync, I get multiple analysis errors, and it also looks like several tests were failing when this was merged. Here are the analysis errors I get on master:
|
Nevermind: this was just cruft left in my repo, after cleaning I get no analysis errors. But why was this committed with failing tests? |
@gspencergoog the errors are unrelated, and due to dnfield/flutter_svg#435. The g3 test is being fixed internally. |
@@ -64,7 +63,11 @@ const Map<String, String> _kManuallyPinnedDependencies = <String, String>{ | |||
// https://github.com/dart-lang/build/issues/2772 | |||
'build_runner_core': '5.2.0', | |||
'build_modules': '2.10.1', | |||
'path_provider': '1.6.14' | |||
'path_provider': '1.6.14', |
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.
why are we pinning path_provider
?
(just asking because i'm adding comments to update_packages.dart
)
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.
I'm not sure why path_provider
was pinned. maybe @jonahwilliams ?
Re-attempts #69238