Repository navigation
feat: use Open Sync 0.5 shared scheduling - #215
Merged
Merged
Conversation
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.
Why
Context Use still embeds Open Sync 0.3.1 and advertises per-sync polling intervals. Open Sync 0.5.0 moves enabled syncs to a shared half-hourly OS schedule and removes the interval and polling-deadline fields.
How
Upgrade to 0.5.0, remove obsolete scheduling metadata from sync creation and managed responses, and show the shared 30-minute schedule in the UI. Await scheduler startup before listening, and compile through a cron-first entrypoint with module splitting so scheduled invocations reach the running worker without initializing another host.
Manual runs, pause/resume, ownership filtering, and local record delivery retain their existing contracts.