You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there seems to be some issues with the time crate when used with hartex-reflect on Linux systems (the following copied from CI):
error[E0433]: failed to resolve: could not find `format_description` in `time`
--> /home/runner/.cargo/git/checkouts/twilight-2be8c306df460cc0/dcadfb5/twilight-model/src/util/datetime/mod.rs:53:12
|
53 | use time::{format_description::well_known::Rfc3339, OffsetDateTime, PrimitiveDateTime};
| ^^^^^^^^^^^^^^^^^^ could not find `format_description` in `time`
error[E0432]: unresolved import `time::error`
--> /home/runner/.cargo/git/checkouts/twilight-2be8c306df460cc0/dcadfb5/twilight-model/src/util/datetime/error.rs:11:11
|
11 | use time::error::{ComponentRange as ComponentRangeError, Parse as ParseError};
| ^^^^^ could not find `error` in `time`
error[E0432]: unresolved imports `time::OffsetDateTime`, `time::PrimitiveDateTime`
--> /home/runner/.cargo/git/checkouts/twilight-2be8c306df460cc0/dcadfb5/twilight-model/src/util/datetime/mod.rs:53:53
|
53 | use time::{format_description::well_known::Rfc3339, OffsetDateTime, PrimitiveDateTime};
| ^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^ no `PrimitiveDateTime` in the root
| |
| no `OffsetDateTime` in the root
error: aborting due to 3 previous errors
However, I cannot reproduce the same issue on Windows and macOS. Given that I do not have a Linux machine lying around, it would be great if someone could look into this.
The text was updated successfully, but these errors were encountered:
Currently, there seems to be some issues with the
time
crate when used withhartex-reflect
on Linux systems (the following copied from CI):However, I cannot reproduce the same issue on Windows and macOS. Given that I do not have a Linux machine lying around, it would be great if someone could look into this.
The text was updated successfully, but these errors were encountered: