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
restate-1 | on rt:pp-23
restate-1 | thread 'rs:worker-2' panicked at /rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58/library/core/src/time.rs:1138:31:
restate-1 | overflow when subtracting durations
restate-1 | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
restate-1 | on rt:pp-18
restate-1 | 2025-02-27T02:59:00.475284Z ERROR tracing_panic
restate-1 | A panic occurred
restate-1 | panic.payload: "overflow when subtracting durations"
restate-1 | panic.location: "/rustc/e71f9a9a98b0faf423844bf0ba7438f29dc27d58/library/core/src/time.rs:1138:31"
restate-1 | panic.backtrace: disabled backtrace
restate-1 | panic.note: "run with RUST_BACKTRACE=1 environment variable to display a backtrace"
The text was updated successfully, but these errors were encountered:
Thanks a lot for reporting this issue @MikeIvanichev. This looks like a bug we need to fix. I am looking into this now. Did you manage to reproduce the problem so that in case we have a fix you could help us trying it out?
Did you run any service when the server crashed? If yes, was the service doing time based operations (e.g. a delayed call, a sleep or something like this)?
I have found two sources that can explain the overflow. I'll fix them and include them in the upcoming 1.2.1 release that I will create today. Once this is out, you can give it a spin.
Ran into an issue where the re-state server hard crashed, this is all the information I was able to salvage:
Version:
Restate Server 1.2.0 (debug) (badad0c x86_64-unknown-linux-gnu 2025-02-14)
Config:
default
Hardware info:
Logs:
The text was updated successfully, but these errors were encountered: