Ramesh Sampath

@flocho-hy @sachinprasadhs @deepdatadive @TheSmileXiao - Release KerasCV 0.9.0. Can you update your KerasCV version by `pip install -U keras-cv` and let me know if you still run into this issue?

@nicolasnn - Thanks for reporting this issue with detailed examples. I am working on an update to `BackupAndRestore` callback to address this specific scenario. I will submit a PR in...

When you use TensorFlow 2.16 with RC0 and testing Keras 2 path, please install `pip install tf-keras~=2.16.0rc0` (will install RC2). If you use `pip install tf-keras` instead, it will install...

When you use [metrics.Accuracy](https://github.com/keras-team/tf-keras/blob/master/tf_keras/metrics/accuracy_metrics.py#L29), it resolves to `BinaryAccuracy` as stated in the doc of `Accuracy`. Whereas, when using string `accuracy` it resolves to BinaryAccuracy or CategoricalAccuracy, based on the target...

The same behavior exists in Keras 3 as well. Should we deprecate use of `metrics.Accuracy` or mimic its usage to string metric of `accuracy`?

Thanks for the issue. Would you be able to contribute with a PR?

Thanks for reporting the issue. I confirm that Release 0.6.0 had the argument named as `masked_positions` https://github.com/keras-team/keras-nlp/blob/r0.6/keras_nlp/layers/modeling/masked_lm_head.py#L180. This is changed in main branch to `mask_positions`, so checking with @mattdangerw to...

After discussing with Matt, I realized that we need to update the arg in tutorial to `masked_positions`. Will update with a PR.

Tagging the author of the tutorial - @rbouadjenek