-
Notifications
You must be signed in to change notification settings - Fork 528
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
Slow initial epoch progress causes time to overflow and program panics #447
Comments
I don't think it's a conversion to u64, since I don't think it can panic. It seems like there is an overflow when adding durations. It's pretty weirds and I'm not able to reproduce. Does it panic everytime you run the example? |
Yes, it panics every time. You'll also see that the epoch epoch and iteration progress bars look quite strange.
Edit: this is also on |
@DevonMorris can you verify that the fix works on your system: #450. I think the problem comes from the time estimation when the first epoch completion is almost instant. |
That didn't work either
I, unfortunately, don't have time to look deeper right now to see if this is a specific issue with my setup. So if you are unable to reproduce, it may be a issue with my local setup. |
I think I can reproduce by waiting for the epoch to complete. The problem comes from the ETA calculated from the indicatif lib, the easy solution is just to remove the ETA or to calculate it ourself. |
Yep. See console-rs/indicatif#556. Verifying that modifying the progress bar template solves: // let bar = "[{wide_bar:.cyan/blue}] ({eta})";
let bar = "[{wide_bar:.cyan/blue}]"; |
I'm going to remove the (eta) from the progress bar and create an issue to add it back when the indicatif issue is resolved. |
Describe the bug
Hi! I was just checking out your examples and experienced a bug. On slow compute and long first epoch, duration overflows on epoch progress bar causing the program to panic.
To Reproduce
Essentially, I just ran the mnist example on
main
Expected behavior
I think this is obvious, it should not panic.
Screenshots
Desktop (please complete the following information):
Additional context
I'm guessing the problem lies here
But not 100% sure
The text was updated successfully, but these errors were encountered: