gabriel/beetask
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix task timer showing negative values

Browse source 
Ensure running seconds never go negative by using Math.max(0, ...)
This prevents the timer from showing negative values when there's a
clock skew between client and server.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This commit is contained in:
Gabriel Santana de Menezes 2026-05-18 09:59:56 -04:00
parent e37cf06634
commit 814bc51b86
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
frontend/src/components/TaskTimer.tsx
View file

@ -49,7 +49,7 @@ export function TaskTimer({ task, onUpdate, canControl = true }: TaskTimerProps)
if (runningItem) { if (runningItem) {
interval = setInterval(() => { interval = setInterval(() => {
const runningSeconds = differenceInSeconds(new Date(), parseISO(runningItem.startAt)) const runningSeconds = Math.max(0, differenceInSeconds(new Date(), parseISO(runningItem.startAt)))
setDisplaySeconds(accumulatedSeconds + runningSeconds) setDisplaySeconds(accumulatedSeconds + runningSeconds)
}, 1000) }, 1000)
} else { } else {
@ -64,7 +64,7 @@ export function TaskTimer({ task, onUpdate, canControl = true }: TaskTimerProps)
// Initial calculation // Initial calculation
useEffect(() => { useEffect(() => {
if (runningItem) { if (runningItem) {
const runningSeconds = differenceInSeconds(new Date(), parseISO(runningItem.startAt)) const runningSeconds = Math.max(0, differenceInSeconds(new Date(), parseISO(runningItem.startAt)))
setDisplaySeconds(accumulatedSeconds + runningSeconds) setDisplaySeconds(accumulatedSeconds + runningSeconds)
} else { } else {
setDisplaySeconds(accumulatedSeconds) setDisplaySeconds(accumulatedSeconds)