Conversation
| Future<void> initialize({bool soundNullSafety}) async {} | ||
|
|
||
| @override | ||
| Future<bool> updateDependencies(Map<String, ModuleInfo> modules) async => true; |
There was a problem hiding this comment.
This code is not used in the monorepo and should be perfectly safe to roll.
There was a problem hiding this comment.
is this something the tool needs to implement? @grouma
There was a problem hiding this comment.
Nope. Since you guys use the Frontend Server your dependencies are always up to date and it is always initialized with the correct null safety support.
|
|
||
| @override | ||
| void dispose() { | ||
| Future<void> dispose() async { |
There was a problem hiding this comment.
I think this code won't cause problems in g3 but it potentially could.
There was a problem hiding this comment.
well, that is what frob is for :)
|
This pull request is not suitable for automatic merging in its current state.
|
|
This is failing due to some package conflicts with the new gallery. |
|
This pull request is not suitable for automatic merging in its current state.
|
|
This is now blocked on Mockito. Currently, there is no version 4.x of Mockito that supports a new enough analyzer to use a null-safe package:crypto. Checking with @srawlins to see if we can do anything about that. If not, we might want to wait on this until after stable release. |
|
Full error text, which is not showing up in CI logs unfortunately, is: |
|
Mockito 4.1.4 was published to help with this. |
|
This pull request is not suitable for automatic merging in its current state.
|
|
Tree is actually green |
This updates vm_service and package:test* in particular.
I have not run all tests on this yet.
I've added some analysis ignores for files that will be rolled into g3 to hopefully make rolls easier.