Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate from chrono to time 0.3 #256

Open
estk opened this issue Apr 22, 2022 · 7 comments
Open

Migrate from chrono to time 0.3 #256

estk opened this issue Apr 22, 2022 · 7 comments
Labels

Comments

@estk
Copy link
Owner

estk commented Apr 22, 2022

No description provided.

@estk estk added the chore label Apr 22, 2022
@Will-Low
Copy link

@estk - #241 appears to provide a quick solution to this.

@Forsworns
Copy link

@estk Any idea about #241? The cve alerts of the outdated time crate persist in the downstream libraries depending on log4rs.

@skull-squadron
Copy link

Bump

@dertin
Copy link

dertin commented Jun 20, 2023

@estk
Are there plans to continue with this migration or was this project abandoned? I would like to know.
I don't have the knowledge to provide a PR.
I hope this package can be improved. thank you!

@bconn98
Copy link
Collaborator

bconn98 commented Feb 10, 2024

Are we still looking to switch to time? We’ve resolved the CVE concern so I believe this is OBE. @dertin @skull-squadron @Forsworns @Will-Low

@estk
Copy link
Owner Author

estk commented Feb 10, 2024

No current work being done on this. Seems like chrono is no longer unmaintained so no need to make the change. Open to input here.

@bconn98
Copy link
Collaborator

bconn98 commented Feb 10, 2024

Definitely in the “if it ain’t broke don’t fix it” camp. If someone comes forward with an example of how it improves the code base, I’m all for it, but otherwise I would hold tight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants