Meteor-Community-Packages / Meteor-Community-Packages/meteor-timesync
Re-sync message in console
Open
Nobody has claimed this yet.
question
- Dominant language
- JavaScript
- Stars
- 119
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Each time my app uses the CPU intensively for a few seconds, I get the following message in the console:
Clock discrepancy detected. Attempting re-sync.
This brings me two questions:
- How does CPU activity relate to sync lost?
- My understanding was that
TimeSync.watchClockChangeswas false by default, preventing re-sync to occur. I tried to force it to false anyway, but it has no effect. How can I prevent re-sync?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the implementation and documentation for TimeSync.watchClockChanges, then inspect where the “Clock discrepancy detected” message is emitted. Reproduce the behavior during sustained CPU activity and determine whether the setting is honored; done means the cause and the supported way to prevent re-sync are explained or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100