fix: make sure wall clock duration is in valid range

Author: nyannyacha

crates/base/src/rt_worker/supervisor/strategy_per_request.rs

@@ -53,8 +53,8 @@ pub async fn supervise(args: Arguments, oneshot: bool) -> (ShutdownReason, i64)
 
     // reduce 100ms from wall clock duration, so the interrupt can be handled before
     // isolate is dropped
-    let wall_clock_duration =
-        Duration::from_millis(runtime_opts.worker_timeout_ms) - Duration::from_millis(100);
+    let wall_clock_duration = Duration::from_millis(runtime_opts.worker_timeout_ms)
+        .saturating_sub(Duration::from_millis(100));
 
     let wall_clock_duration_alert = tokio::time::sleep(wall_clock_duration);
 

crates/base/src/rt_worker/supervisor/strategy_per_worker.rs

@@ -48,8 +48,8 @@ pub async fn supervise(args: Arguments) -> (ShutdownReason, i64) {
 
     // reduce 100ms from wall clock duration, so the interrupt can be handled before
     // isolate is dropped
-    let wall_clock_duration =
-        Duration::from_millis(runtime_opts.worker_timeout_ms) - Duration::from_millis(100);
+    let wall_clock_duration = Duration::from_millis(runtime_opts.worker_timeout_ms)
+        .saturating_sub(Duration::from_millis(100));
 
     // Split wall clock duration into 2 intervals.
     // At the first interval, we will send a msg to retire the worker.