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.

Sign up for GitHub

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

Jump to bottom

Maintenance Status #31

Open
pinkforest opened this issue Aug 4, 2022 · 5 comments · May be fixed by #32
Open

Maintenance Status #31

pinkforest opened this issue Aug 4, 2022 · 5 comments · May be fixed by #32

Comments

@pinkforest
Copy link

pinkforest commented Aug 4, 2022 •
edited
Loading

Hi @tailhook just wondering what is the maintenance status around humantime ?

It's using rather old version of time ^0.1 ? the current 0.1 is 0.1.42 over 3 years ago - dev has moved to 0.3

Appreciate they are just development deps but anyways 🤷‍♀️

src/date.rs: let s = time::at_utc(time::Timespec { sec: sec as i64, nsec: 0 })
And rand would be best idea to bump to 0.8 .. 0.6 is using oudated deps

src/duration.rs:    use rand::Rng;
src/duration.rs:    fn random_second() {
src/duration.rs:            let sec = rand::thread_rng().gen_range(0, 253_370_764_800);
src/duration.rs:    fn random_any() {
src/duration.rs:            let sec = rand::thread_rng().gen_range(0, 253_370_764_800);
src/duration.rs:            let nanos = rand::thread_rng().gen_range(0, 1_000_000_000);
src/date.rs:    use rand::Rng;
src/date.rs:    fn random_past() {
src/date.rs:            let sec = rand::thread_rng().gen_range(0, upper);
src/date.rs:    fn random_wide_range() {
src/date.rs:            let sec = rand::thread_rng().gen_range(0, max::SECONDS);

Could we bump time to ^0.3 and rand to ^0.8 - I sent a PR:
#32
@pinkforest pinkforest linked a pull request Aug 4, 2022 that will close this issue
Open
@mre mre mentioned this issue Oct 24, 2022
Closed
@guilload
Copy link

@tailhook, could you add some maintainers to the project? I'm happy to help. @pinkforest, any interest?

@pinkforest
Copy link
Author

pinkforest commented Jun 23, 2023 •
edited
Loading

I propose we fork and call it cyborgtime, I created cyborg-rs - have this idea to cybernetically enhanche maintenance chores 📦

If the maintainer wakes up they can propagate upstream

@guilload
Copy link

go for cyborgtime.

@pinkforest pinkforest mentioned this issue Jun 23, 2023
Merged
@grinapo
Copy link

grinapo commented Oct 29, 2024

Hmm, yes but cyborgtime does have its issue management disabled... so whatever issues we have here around they still stay ignored over there (or anywhere).

@pinkforest
Copy link
Author

fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Chore/bump time rand pinkforest/humantime
3 participants
@grinapo @guilload @pinkforest