warning: an implementation of `From` is preferred since it gives you `Into<_>` for free where the reverse isn't true --> src/data_model/time.rs:10:1 | 10 | impl Into<Duration> for Milliseconds { | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: `impl From<Local> for Foreign` is allowed by the orphan rules, for more information see https://doc.rust-lang.org/reference/items/implementations.html#trait-implementation-coherence = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#from_over_into = note: `#[warn(clippy::from_over_into)]` on by default help: replace the `Into` implementation with `From<data_model::time::Milliseconds>` | 10 ~ impl From<Milliseconds> for Duration { 11 ~ fn from(val: Milliseconds) -> Self { 12 ~ Duration::try_milliseconds(val.0).unwrap() |

warning: an implementation of `From` is preferred since it gives you `Into<_>` for free where the reverse isn't true --> src/data_model/time.rs:10:1 | 10 | impl Into<Duration> for Milliseconds { | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: `impl From<Local> for Foreign` is allowed by the orphan rules, for more information see https://doc.rust-lang.org/reference/items/implementations.html#trait-implementation-coherence = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#from_over_into = note: `#[warn(clippy::from_over_into)]` on by default help: replace the `Into` implementation with `From<data_model::time::Milliseconds>` | 10 ~ impl From<Milliseconds> for Duration { 11 ~ fn from(val: Milliseconds) -> Self { 12 ~ Duration::try_milliseconds(val.0).unwrap() |

warning: associated function `new` is never used --> src/data_model/time.rs:35:12 | 34 | impl Timespan { | ------------- associated function in this implementation 35 | pub fn new(start: DateTimeUtc, end: DateTimeUtc) -> Self { | ^^^ | = note: `#[warn(dead_code)]` on by default

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions-rs/clippy-check@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.