Pin orbax-checkpoint to 0.11.23 to avoid compatibility issue with jax==0.5.3 #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses a dependency conflict that can occur when users have
jax==0.5.3installed and do not specify an upper bound for theorbax-checkpointdependency.The issue is as follows:
flow-rlcurrently requiresjax==0.5.3and does not specify an upper bound for theorbax-checkpointdependency.orbax-checkpointversion0.11.24introduced a call tojax.monitoring.record_scalar, which only exists injax>=0.6.0.orbax-checkpointversion0.11.24did not enforce ajax>=0.6.0dependency, allowing it to be installed alongsidejax==0.5.3.orbax-checkpointversion0.11.25corrected this by adding thejax>=0.6.0requirement, version0.11.24remains available on PyPI, leading to installation and runtime failures for users with the current dependency setup offlow-rl.Solution: This PR pins the
orbax-checkpointdependency to0.11.23, the newest version which does not requirejax>=0.6.0.