[WIP] Refactor GlobalTimer to add schedule tolerance and safe iteration#44
Merged
rsyncOSX merged 1 commit intoglobaltimerfrom Oct 15, 2025
Merged
Conversation
Copilot stopped work on behalf of
rsyncOSX due to an error
October 15, 2025 13:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Original prompt
Refactor GlobalTimer to add per‑schedule tolerance, safe iteration during callbacks, and wake debounce (Swift 6).
Context
The project already contains a GlobalTimer implementation used by the macOS app target. The current version runs a one‑shot foreground timer and reacts on system wake. We want to keep this simpler approach (no NSBackgroundActivityScheduler), but make it safer and a bit more precise.
Required changes
File to replace
Paste the following full content into GlobalTimer.swift.