fix(working_time): compute duration for segments starting at midnight

[0xD0M1M0]

Working Time Log rows with from_time 00:00:00 kept duration 0 even when to_time was later the same day. Parent Working Time totals then ignored that segment.

Cause:
set_duration (and related helpers) used if self.from_time. timedelta(0) is falsy in Python, so midnight was skipped.

Reproduce:

1. Create a Working Time with a log row from 00:00:00 to a later time (e.g. 07:44:00).
2. Save the document.
3. Row duration stays 0; working_time / project_time only include other rows.

Fix:
use is not None instead of truthiness for from_time and to_time.

[greptile-apps]

Confidence Score: 5/5

Safe to merge — a minimal, targeted fix to a well-described calculation bug with no side effects on existing valid inputs.

The change is small and surgical: three guard conditions updated to use explicit None checks instead of truthiness. The only behaviorally significant change is in set_duration, where timedelta(0) being falsy caused midnight start times to silently produce zero duration. All other changes are either no-ops or stylistically equivalent.

No files require special attention.

Sequence Diagram

sequenceDiagram
    participant Caller
    participant WorkingTimeLog
    Caller->>WorkingTimeLog: cleanup_and_set_duration()
    WorkingTimeLog->>WorkingTimeLog: ensure_timedelta() str 00:00:00 to timedelta(0)
    WorkingTimeLog->>WorkingTimeLog: remove_seconds() guard is not None
    WorkingTimeLog->>WorkingTimeLog: uppercase_key()
    WorkingTimeLog->>WorkingTimeLog: set_duration() guard is not None duration computed

Loading

_{Reviews (1): Last reviewed commit: "fix(working_time): compute duration for ..." | Re-trigger Greptile}

[barredterra]

🎉 This PR is included in version 15.4.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀