ChronoDateExt::quarter() conflicts with chrono v0.4.40

[yutannihilation]

Describe the bug

chrono v0.4.40, which was released just a few hours ago, provides its own .quarter() method.

pull request: chronotope/chrono#1666

So, this now conflicts with the arrow's implementation.

error[E0034]: multiple applicable items in scope
   --> /Users/yutannihilation/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/arrow-arith-54.2.0/src/temporal.rs:92:36
    |
92  |         DatePart::Quarter => |d| d.quarter() as i32,
    |                                    ^^^^^^^ multiple `quarter` found
    |
note: candidate #1 is defined in the trait `ChronoDateExt`
   --> /Users/yutannihilation/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/arrow-arith-54.2.0/src/temporal.rs:638:5
    |
638 |     fn quarter(&self) -> u32;
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^
note: candidate #2 is defined in the trait `Datelike`
   --> /Users/yutannihilation/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/chrono-0.4.40/src/traits.rs:47:5
    |
47  |     fn quarter(&self) -> u32 {
    |     ^^^^^^^^^^^^^^^^^^^^^^^^
help: disambiguate the method for candidate #1
    |
92  |         DatePart::Quarter => |d| ChronoDateExt::quarter(&d) as i32,
    |                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~
help: disambiguate the method for candidate #2
    |
92  |         DatePart::Quarter => |d| Datelike::quarter(&d) as i32,
    |                                  ~~~~~~~~~~~~~~~~~~~~~

For more information about this error, try `rustc --explain E0034`.
error: could not compile `arrow-arith` (lib) due to 1 previous error

To Reproduce

cargo update chrono
cargo build

Expected behavior

Additional context

[ddimaria]

This issue is blocking our builds. I saw there was a fix applied in #7198, does anyone know when this will be released?

[tustvold]

Unfortunately chrono released a breaking change in a patch release, whilst #7198 updates to accomodate this breaking change, downstreams will need to pin to chrono v0.4.39 either using a lockfile or an explicit dependency

[haixuanTao]

For a hot quick fix, this should work:

arrow = { git = "https://github.com/apache/arrow-rs" }
arrow-schema = { git = "https://github.com/apache/arrow-rs" }
arrow-data = { git = "https://github.com/apache/arrow-rs" }
arrow-array = { git = "https://github.com/apache/arrow-rs" }

But, this is just for currently build on git.

I wonder if this issue makes old version of arrrow by default unusable, as well as all package like mine dependant on arrow.

[tustvold]

For a hot quick fix, this should work:

A simpler option would be

chrono = "= 0.4.39"

Anywhere in the workspace

I wonder if this issue makes old version of arrrow by default unusable, as well as all package like mine dependant on arrow.

They'll work fine provided something, e.g. lockfile or constraint, encourages cargo to not use 0.4.40

[DataBora]

I needed to downgrade DataFusion from 44.0.0 to 43.0.0, arrow to =53.2.0, and chrono to =0.4.38 , in order for Elusion crate to build. I had consideration for ODBC as well, so thats why chrono is on 0.4.38