-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[CP][stable channel] Fix null-safety issue in VM's typed-data + operators. #45156
Comments
@lrhn I switched out to the current version of template. Can you add a line for the Why cherrypick section? |
The early consensus from offline chat is that this is not very urgent. |
@mraleph |
Is this a known regression from 2.10? Seems a reasonable thing to queue up for a dot-1 release |
lgtm |
1 similar comment
lgtm |
Hot fixed approved. Text description: This fix a bug in the VM typed_data operator that result in runtime crash, see issue #45140. |
Hot fix 2.12.1 |
commit(s) to merge: eb6b474
merge instructions: clean merge
What is the issue: VM typed_data. The typed data list
+
operator did not work.What is the fix: Fixes bug in null safety migration of VM typed_data. The typed data list
+
operator did not work.See issue #45140.
Why cherrypick: It's a broken feature in the platform libraries. Any code which uses the feature will crash at run-time.
There is likely not much code which uses the feature, since we haven't discovered the bug earlier, but at least one user
has hit it.
Risk: Low
Link to original issue(s): #45140
/cc @kevmoo @mit-mit @whesse @athomas @vsmenon @franklinyow
@whesse
The text was updated successfully, but these errors were encountered: