Fixed
Status Update
No update yet.
Comments
hi...@google.com
bl...@google.com
Project: platform/frameworks/support
Branch: androidx-main
Author: Kuan-Ying Chou <
Link:
Remove ToT dependencies in wear:compose:compose-navigation
Expand for full commit details
Remove ToT dependencies in wear:compose:compose-navigation
Bug: 374102924
Test: n/a
Change-Id: Id057c7254a0282eab77a2facb4d278e3b5ccf784
Files:
- M
wear/compose/compose-navigation/samples/build.gradle
Hash: 285f596b323a37b82e07621acb990847b8cf4328
Date: Thu Oct 31 13:36:53 2024
hi...@google.com
Project: platform/frameworks/support
Branch: androidx-main
Author: Kuan-Ying Chou <
Link:
Update Kotlin targets to 1.9
Expand for full commit details
Update Kotlin targets to 1.9
Update Kotlin target of savedstate and projects that depend on it to 1.9.
Bug: 374102924
Test: existing tests still pass
Change-Id: I442310ec57f7db381c16f95985a952deb9af57b2
Files:
- M
lifecycle/lifecycle-viewmodel-compose/build.gradle - M
lifecycle/lifecycle-viewmodel-compose/samples/build.gradle - M
lifecycle/lifecycle-viewmodel-savedstate/build.gradle - M
lifecycle/lifecycle-viewmodel-testing/build.gradle - M
savedstate/savedstate-ktx/build.gradle - M
savedstate/savedstate/build.gradle - M
savedstate/savedstate/src/nativeMain/kotlin/androidx/savedstate/internal/SynchronizedObject.native.kt
Hash: 73305d3cf9d9bfff42b1836ac0127032b7721496
Date: Tue Oct 29 17:27:51 2024
zm...@google.com
Project: platform/frameworks/support
Branch: androidx-main
Author: Kuan-Ying Chou <
Link:
Add functions to encode serializable objects to and decode serializable objects from SavedState.
Expand for full commit details
Add functions to encode serializable objects to and decode serializable objects from `SavedState`.
We do this by implementing an `Encoder` and a `Decoder` that writes and reads a `SavedState` output format for Kotlin Serialization (https://github.com/Kotlin/kotlinx.serialization). The format represents a Kotlin Serialization "primitive" as their corresponding `SavedState` supported type, and represents a "composite" in a `SavedState` with its property names as keys. Nested composites are represented by nested `SavedState`s.
Here are some other design choices we made:
1. We don't record size for collections and rely on the size of the `SavedState` in decoding so that collections and non-collections are treated the same.
2. To save space, we don't encode default values by default (it can be tweaked with `@EncodeDefault` with plugin-generated serializers).
3. To support nullable parameters with default arguments (e.g. `val a: String? = "foo"`) and for `SavedState` size to be correct for collections, we encode `null`s.
4. To keep things simple we don't support specifying custom `SerializersModule`s for now.
Please note that when using Kotlin Serialization and these functions as a `Parcelable` alternative on Android there's a performance overhead because of the extra serialization needed.
Also note that on Android we don't have built-in support for Android or Java specific types supported by `Bundle` or `Parcel` yet (e.g. `Exception`, `java.io.Serializable`, or `IBinder`). We may consider adding these types in the future.
Relnote: Add encodeToSavedState() and decodeFromSavedState() functions
Test: SavedStateCodecTest.kt
Bug: 374102924
Change-Id: I6f59faffaa3777bf56132a67f41b867d7a9663e5
Files:
- M
development/build_log_simplifier/messages.ignore - M
docs-tip-of-tree/build.gradle - A
savedstate/savedstate-samples/build.gradle - A
savedstate/savedstate-samples/src/main/java/androidx/savedstate/SavedStateCodecSamples.kt - M
savedstate/savedstate/api/current.txt - M
savedstate/savedstate/api/restricted_current.txt - M
savedstate/savedstate/bcv/native/current.txt - M
savedstate/savedstate/build.gradle - A
savedstate/savedstate/src/androidUnitTest/kotlin/androidx/savedstate/SavedStateCodecAndroidTest.android.kt - A
savedstate/savedstate/src/commonMain/kotlin/androidx/savedstate/serialization/SavedStateDecoder.kt - A
savedstate/savedstate/src/commonMain/kotlin/androidx/savedstate/serialization/SavedStateEncoder.kt - A
savedstate/savedstate/src/commonTest/kotlin/androidx/savedstate/SavedStateCodecTest.kt - A
savedstate/savedstate/src/commonTest/kotlin/androidx/savedstate/SavedStateCodecTestUtils.kt - M
settings.gradle
Hash: 57162ea74b646ef7ae43397251fd4cd32e2d80c3
Date: Thu Oct 17 19:10:05 2024
aa...@gmail.com
Good news! Wear Compose has been updated to ab/12605136 in https://critique.corp.google.com/cl/693389210 and this bug has been affected.
[Deleted User] <[Deleted User]>
I'm not sure if this is the same issue, but when i was doing a groupinstall using:
dnf groupinstall "Server with GUI" -- after doing this, i would reboot the machine and it would never come back up, it kept complaining that the OSConfig agent was failing to boot up, it would never get to the login screen or allow me to SSH into the server, as the SSHD daemon hadn't started by that point. Connecting in via serial port does work, as long as the root password is set before you reboot after updates have been run. also when this happens this VM can't get out to the internet. this occurred on RHEL 8. not sure if this is relevant or not to the issue, but its almost like the groupinstall drops the static IP i had assigned to the VM and i've had to use window's VMs due to this problem.
dnf groupinstall "Server with GUI" -- after doing this, i would reboot the machine and it would never come back up, it kept complaining that the OSConfig agent was failing to boot up, it would never get to the login screen or allow me to SSH into the server, as the SSHD daemon hadn't started by that point. Connecting in via serial port does work, as long as the root password is set before you reboot after updates have been run. also when this happens this VM can't get out to the internet. this occurred on RHEL 8. not sure if this is relevant or not to the issue, but its almost like the groupinstall drops the static IP i had assigned to the VM and i've had to use window's VMs due to this problem.
je...@microdinc.com
Still facing this issue. Once you run yum update the instance is unavailable Running Centos 7
ch...@enviemedia.com
anyone find a way to fix this?
ma...@gmail.com
I am affected with this as well. Has anyone find a workaround?
fg...@google.com
we...@gmail.com
Does google have a plan to resolve this for affected machines? We can't exactly restore them with a RHEL DVD as proposed by redhat....
fa...@gmail.com
After 48 hours of this incident and Google has not solved this problem-
we...@gmail.com
How they did not notify users is mind-blowing. Lost 2 full days of work after rebooting this morning. The proposed "solutions" don't work, wasted several hours restoring snapshots, and attempting solutions only to have the system freeze at POST. Completely unacceptable.
lu...@gcp.somosnuvem.com.br
Enfim, sem saber do problema. Agora estou com um cliente afetado pelo mesmo.
ma...@gmail.com
It has been a frustrating 2 days...
se...@gmail.com
Still unsolved...
sa...@etcc.com
The work around provided does not resolve the issue. I mounted the boot disk to another VM, chroot into it, and downgraded. The same boot error still occurred.
ba...@gmail.com
in...@larsendigital.dk
When is this expected to be resolved?
we...@gmail.com
Any updates? I restored a snapshot but am waiting to be able to update. Also would be nice if it's possible to recover the 15+ hours of work I lost.
vi...@gmail.com
In my case I had to change temporarily the affected build's script to exclude shim-x64 from the updates. Any centos-7 image built with this shim affected version shim-x64-15-7.el7_9.x86_64 gets locked and unusable.
When the solution comes up I will revert this change.
When the solution comes up I will revert this change.
na...@gmail.com
Although after downgrading the shim, my VM did boot up, but can someone confirm that the shim update containing the bug will not be applied to my VM if I reboot again today.
ma...@gmail.com
Hey Google, any update on this?
st...@google.com
st...@google.com
Updates have been rolled out by Redhat and CentOS. If your instance is booting correctly, you can update to the following shim versions:
RHEL 7: shim-x64-15-8.el7_8.x86_64
RHEL 8: shim-x64-15-15.el8_2.x86_64
CentOS 7: shim-x64-15-8.el7.x86_64
CentOS 8: shim-x64-15-15.el8_2.x86_64
You can see current version with rpm -q shim-x64. Do not update to a lower version than those given above.
If your machine is currently hung at boot, you will need to copy the shim from a working machine. See the instructions in
UPDATE: Previously the package for RHEL 7 had not rolled out. At this time packages are available for all OS versions affected.
UPDATE 2: see
st...@google.com
The updated packages from
fa...@gmail.com
hello google (st...@google.com), my instance does not turn on. How can I carry out the "yum update shim-x64" update? In comment # 25 you mention that the machines require intervention to boot again.
Excuse me, but your message is very concise- how come it should have an intervention to boot again, what do you mean?
If you can explain the procedure in more detail I would appreciate it.
Thank you!
Excuse me, but your message is very concise- how come it should have an intervention to boot again, what do you mean?
If you can explain the procedure in more detail I would appreciate it.
Thank you!
id...@gmail.com
so desperate, is out there step by step tutorial how to fix this issue?
help please!
help please!
st...@google.com
Instructions for recovering a hung machine:
Backup impacted instance
Before doing anything, snapshot the impacted disk! Mistakes happen.
Example (see gcloud compute disks snapshot --help for all options or use the Cloud Console):
gcloud compute disks snapshot DISK_NAME --zone ZONE --snapshot-names=NAME
Build rescue instance
Create a new instance with the same OS as the damaged disk in the same zone as the damaged disk. An instance from a new image won't have the updates applied and therefore should boot without hanging.
Add the impacted disk as a additional disk to the rescue machine
- Stop the impacted instance (the one that hangs at boot).
- Edit the impacted instance in the Cloud Console and remove its boot disk
- Edit the rescue instance and attach the impacted boot disk as an additional disk.
- SSH'd into the rescue machine, mount the EFI boot partition of the impacted instance to /mnt. Assuming you have only attached one disk and these are Google images, you need to
mount /dev/sdb1 /mnt. You can uselsblkto determine the actual device name.
Repair the impacted disk
RHEL
cp /boot/efi/EFI/redhat/shimx64.efi /mnt/EFI/redhat/
CentOS
cp /boot/efi/EFI/centos/shimx64.efi /mnt/EFI/centos/
Repair impacted instance
- Unmount the disk from rescue instance:
umount /mnt - Detach impacted disk from rescue instance.
- Attach disk as boot disk to impacted instance
- Start impacted instance
- Optional: snapshot again. Can't be too careful.
- On impacted instance, update to a known working version of the shim:
yum update shim-x64 - Reboot to make sure machine still boots.
ev...@scailyte.com
Were only instances with activated VTPM affected?
fa...@gmail.com
st...@google.com, thanks for you help on
st...@google.com
This issue is now locked. For a list of affected shim-64 versions, see
For instructions on how to fix an instance that is currently unable to boot, see
Description
After applying latest CentOS 7 updates, the instance is un-bootable.
What you expected to happen:
Steps to reproduce:
Create a CentOS 7 vm
update (sudo yum update)
reboot
Other information (workarounds you have tried, documentation consulted, etc):
!!!! X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - 00000000 !!!!
ExceptionData - 0000000000000000
RIP - 00000000BF2E6D5C, CS - 0000000000000038, RFLAGS - 0000000000010006
RAX - 00000000BFF67E50, RCX - 000000000000001F, RDX - 00000000BFF39F28
RBX - 00000000BF352FB0, RSP - 00000000BFF39E50, RBP - 00000000000023C0
RSI - 00000000BFF39F28, RDI - 0000000000000068
R8 - 00000000BDB79018, R9 - 000000000000211E, R10 - 00000000BDC59010
R11 - 00000000BFF39E9A, R12 - 00000000BE757068, R13 - 00000000BF339018
R14 - 00000000BEE21018, R15 - 0000000000000068
DS - 0000000000000030, ES - 0000000000000030, FS - 0000000000000030
GS - 0000000000000030, SS - 0000000000000030
CR0 - 0000000080010033, CR2 - 0000000000000000, CR3 - 00000000BF401000
CR4 - 0000000000000668, CR8 - 0000000000000000
DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
GDTR - 00000000BF3EEA98 0000000000000047, LDTR - 0000000000000000
IDTR - 00000000BEE1F018 0000000000000FFF, TR - 0000000000000000
FXSAVE_STATE - 00000000BFF39AB0
!!!! Find image based on IP(0xBF2E6D5C) /build/work/af60adde42b1d1ad5be2a01e4924bb905248/google3/blaze-out/k8-opt/genfiles/third_party/edk2/ovmf_x64_csm_debug_workspace_dir/ovmf_x64_csm_debug_edk2_files_dir/Build/OvmfX64/DEBUG_CLANG38/X64/OvmfPkg/8254TimerDxe/8254Timer/DEBUG/Timer.dll (ImageBase=00000000BF2E5000, EntryPoint=00000000BF2E6AB5) !!!!