-
Notifications
You must be signed in to change notification settings - Fork 28.5k
Latest Dart roll blocked by deprecated code in the engine #137054
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
Comments
Likely due to https://dart-review.googlesource.com/c/sdk/+/321922 This issue was caught on Friday morning by the monorepo builder: https://ci.chromium.org/ui/p/dart/builders/ci.sandbox/flutter-linux-flutter-plugins/1367/overview. |
Flutter makes it impossible to deprecate something and introduce the replacement in the same CL. Need to first introduce the replacement, then migrate Flutter, and then deprecate. |
revert CL here: https://dart-review.googlesource.com/c/sdk/+/331680 |
This reverts commit b657773. Reason for revert: blocking Dart SDK -> Engine roll (flutter/flutter#137054) Original change's description: > [typed_data] Deprecate UnmodifiableUint8ListView and friends > > This is the first of several steps to remove the unmodifiable views for typed data classes. The end goal is that dart2js has only one class implementing `Uint8List` so that `Uint8List` accesses can always be compiled down to JavaScript code that directly uses indexed property accesses (`a[i]`). > > This first step deprecates the unmodifiable view classes to help prevent their use in new code, and adds `asUnmodifiableView()` methods as a replacement for the small number of places that use the classes. > > The next steps (see #53785) are to remove uses of the unmodifiable view classes from the SDK. Once this is complete the classes themselves can be removed. > > TEST=ci > > Issue: #53218 > Issue: #53785 > > Change-Id: I04d4feb0d9f1619e6eee65236e559f5e6adf2661 > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/321922 > Reviewed-by: Nicholas Shahan <[email protected]> > Reviewed-by: Lasse Nielsen <[email protected]> > Commit-Queue: Stephen Adams <[email protected]> > Reviewed-by: Alexander Markov <[email protected]> > Reviewed-by: Martin Kustermann <[email protected]> > Reviewed-by: Ömer Ağacan <[email protected]> Issue: #53218 Issue: #53785 Change-Id: I0bb042269f9ff8e5cd69619cf97b60c79ea98cbf Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/331680 Bot-Commit: Rubber Stamper <[email protected]> Reviewed-by: Martin Kustermann <[email protected]> Commit-Queue: Derek Xu <[email protected]>
Never mind, I see the reports of other failures. They are already being patched, though. |
I am going to revert the revert, but without the deprecation annotations. Then someone can change the Flutter engine to use the new API. |
xref go/137054-chat |
This is the reapplication of the reverted CL with the Once that lands it will be possible to change
to
|
Here is the list of Unmodifiable hits currently in the our repos: List of `Unmodifiable` references in the engine repo
List of `Unmodifiable` references in the framework repo
|
Thanks for the lists.
This needs to be changed. Perhaps to a try-catch containing an attempted write of a byte that was accessed from the result.
The migration for this is described two messages above.
These should work unchanged.
Change these to
These wrapper views are unrelated to the deprecated typed_data classes. No change needed. |
CL available: flutter/engine#47276 |
Fixed in flutter/engine#47276 |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
See: flutter/engine#47175
Failure at:
The text was updated successfully, but these errors were encountered: