Calculate time_since_last_sync in UTC time.

[Hatell]

Fixes issue when DST is changed between calculation.

[Copilot]

Pull Request Overview

This PR fixes a DST (Daylight Saving Time) issue in the scheduler by ensuring time calculations use UTC instead of local time. This prevents incorrect time_since_last_sync calculations when DST transitions occur between sync operations.

Key Changes:

• Modified current_time to use UTC timezone instead of naive local time

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[auvipy]

can you please also add test to verify the change? can you also link relevant issue as well?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.18%. Comparing base (ba33a9c) to head (ba59d2c).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #964   +/-   ##
=======================================
  Coverage   88.18%   88.18%           
=======================================
  Files          32       32           
  Lines        1007     1007           
  Branches      105      105           
=======================================
  Hits          888      888           
  Misses        101      101           
  Partials       18       18           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[auvipy]

please also check the failing tests due to this change

[cclauss]

https://docs.python.org/3/library/datetime.html#datetime.UTC was added in Python 3.11.

[auvipy]

we still need some additional unit tests

[Hatell]

I make test to this. When drafting test I noticed that int(time.time()) might be better in this use case.