Deprecate get_logical_axis_rule_from_config#4568
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
61f962b to
a316124
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
🤖 Hi @NuojCheng, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
|
🤖 I'm sorry @NuojCheng, but I was unable to process your request. Please see the logs for more details. |
a316124 to
9a2e5c6
Compare
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
| from maxtext.utils.sharding import create_sharding | ||
| from maxtext.utils.sharding import maybe_shard_with_logical | ||
| from maxtext.utils.sharding import get_logical_axis_rules_from_config | ||
| from maxtext.utils.sharding import get_logical_axis_rules |
There was a problem hiding this comment.
do other models need this update?
There was a problem hiding this comment.
Only models with explicit sharding onboarded have this change. I updated some other files to make sure get_logical_axis_rules are used.
9a2e5c6 to
86cd649
Compare
Description
This PR deprecates the
get_logical_axis_rules_from_configfunction insharding.py. In future, we should useutils.sharding.get_logical_axis_rulesto grab logical rule in context.FIXES: b/536927795
Tests
CI test
Checklist
Before submitting this PR, please make sure (put X in square brackets):
gemini-reviewlabel.