Conversation
syncEphemeral used a hardcoded 600ms default while fetchLoop (persistent) used 1200ms. Both now reference DEFAULT_SCHEDULE.pageDelayMs (1200ms) as the single source of truth. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Problem
syncEphemeralused a hardcoded 600ms page delay whilefetchLoop(used by persistent sync) used 1200ms. This inconsistency meant ephemeral connectors made API requests twice as fast as persistent ones, with no clear reason for the difference.Fix
Both now reference
DEFAULT_SCHEDULE.pageDelayMs(1200ms) as the single source of truth. ThedelayMsoption inSyncOptionsstill allows per-call overrides.Test plan
npx tsc --noEmitpasses🤖 Generated with Claude Code