pierre-warnier commented on issue #292:
URL: 
https://github.com/apache/arrow-rs-object-store/issues/292#issuecomment-6948096835

   Reopening this discussion: the reason for closing it no longer holds.
   
   `humantime` is flagged unmaintained again by 
[RUSTSEC-2026-0542](https://rustsec.org/advisories/RUSTSEC-2026-0542.html) (all 
versions, no patched release), following the soft-deprecation of `chrono` in 
chronotope/chrono#1768. Downstream users running `cargo deny` / `cargo audit` 
now see this advisory through `object_store`, which only uses `humantime` to 
parse and format the duration config values (`timeout`, `connect_timeout`, 
`pool_idle_timeout`, ...) in `src/config.rs`.
   
   This was closed in 2025 because `humantime` had found a maintainer again. 
That is no longer the case, and `jiff` 1.0.0 has since been released (MSRV 
1.85, same as `object_store`).
   
   **Describe the solution you'd like**
   
   Replace `humantime` with `jiff`'s `friendly` duration format, without 
changing the public API:
   
   - parsing keeps accepting the existing formats (`60s`, `60 seconds`, `1h 
30m`, `500ms`, `1.5s`, `0`, and calendar units `d`/`w`/`month`/`y` with the 
same day/week/month/year lengths as `humantime`);
   - formatting (`get_config_value`) produces strings that parse back to the 
same `Duration`.
   
   A handful of unusual inputs would behave differently (e.g. `1M` as month, 
repeated or out-of-order units such as `1h 1h`, fractional days); I'll list 
them precisely in the PR, with tests.
   
   **Describe alternatives you've considered**
   
   - Keep `humantime` and have every downstream ignore the advisory.
   - A small hand-written parser instead of a new dependency.
   
   I'm happy to open the PR.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to