Published event
Hardware
SecurityIncident
1 source(s)
TensorFlow 2.11.0
Summary
TensorFlow 2.11.0 tensorflow / tensorflow Public Notifications You must be signed in to change notification settings Fork 77.6k Star 200k TensorFlow 2.11.0 tensorflow-jenkins released this 18 Nov 06:01 · 95 commits to r2.11 since this release v2.11.0 d5b57ca This commit was created on GitHub.com and signed with GitHub’s verified signature . GPG key ID: 4AEE18F83AFDEB23 Expired Verified Learn about vigilant mode .
Why it matters
This SecurityIncident is relevant to the technology intelligence record because it involves GitHub, Intel, Apple, Google. The source article should remain the factual reference for follow-up coverage.
Key facts
- tensorflow / tensorflow Public Notifications You must be signed in to change notification settings Fork 77.6k Star 200k TensorFlow 2.11.0 tensorflow-jenkins released this 18 Nov 06:01 · 95 commits to r2.11 since this release v2.11.0 d5b57ca This commit was created on GitHub.com and signed with GitHub’s verified signature .
- GPG key ID: 4AEE18F83AFDEB23 Expired Verified Learn about vigilant mode .
- Release 2.11.0 Breaking Changes The tf.keras.optimizers.Optimizer base class now points to the new Keras optimizer, while the old optimizers have been moved to the tf.keras.optimizers.legacy namespace.
- If you find your workflow failing due to this change, you may be facing one of the following issues: Checkpoint loading failure.
- The new optimizer handles optimizer state differently from the old optimizer, which simplifies the logic of checkpoint saving/loading, but at the cost of breaking checkpoint backward compatibility in some cases.
- If you want to keep using an old checkpoint, please change your optimizer to tf.keras.optimizer.legacy.XXX (e.g.
Entities in this story
Related events