I’d like to offer a different perspective on the MagSafe LED change that shipped in macOS 26.5. Previously, the LED stayed amber while the battery was below 100%, even when a Charge Limit (e.g. 80%) was active and charging had stopped. Green only appeared at a true 100% charge. After 26.5, green now means “charge limit reached.” While the new behavior might be more consistent with the system’s internal state, it removes a useful visual distinction for users who deliberately keep a limit set for battery longevity: Amber → safe to leave plugged in (either still charging or holding at the limit) Green → truly at 100% (time to unplug if desired) With the current behavior there is no longer a glanceable way to know whether the Mac is holding at the user-set limit or has been allowed to reach 100% (at the periodic calibration charge). Would it be possible to add a preference that lets the user choose when the LED turns green? Green = charge limit reached (current 26.5 behavior) Green = true 100% only (pre-26.5 behavior) This would preserve the improved clarity for those who prefer the new mapping while restoring the previous signal for those of us who relied on it. I’ve already submitted this as Feedback, but wanted to surface the opposing use case here as well. Thanks for considering it.

Getting the same error when working with 64-bit float variables. Minimal example: import tensorflow as tf DTYPE = "float64" def mre(): P = tf.Variable(tf.ones(shape=(), dtype=DTYPE)) delta = tf.ones(dtype=DTYPE, shape=P.shape) print(f"{P.numpy()=}") print(f"{P.dtype=}") P.assign_add(delta) # crashes here print(P.numpy()) if __name__ == "__main__": mre() Environment: Python 3.11.7 tensorflow 2.15.0 tensorflow-estimator 2.15.0 tensorflow-io-gcs-filesystem 0.36.0 tensorflow-macos 2.15.0 tensorflow-metal 1.1.0 Chip: M3 Pro OS: 14.4.1 (23E224)