Restrict chrono dependency to fix arrow build #839
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Restricts the chrono dependency to
>=0.4.34,<0.4.40to fix apache/arrow-rs#7196. This was not impacting arroyo itself, as we use a lockfile, but it did impact UDF compilation for new deployments. This was fixed by pushing an arroyo-udf-common update (0.2.1) with the chrono dependency, although users who ended up with a lockfile from the past two days may need to manually clean out their UDF build directory.This change also remove the fixed version on arroyo-udf-plugin that we generate in the UDF compilation crate, which will give us more tools to respond to these sorts of upstream breakages in the future.