Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

cpvalente / ontime Public

Notifications You must be signed in to change notification settings
Fork 56
Star 545

Code
Issues 30
Pull requests 10
Discussions
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Better update rate and batch in client#1295

Open

alex-Arc wants to merge 6 commits intomastercpvalente/ontime:masterfrom timer-synccpvalente/ontime:timer-syncCopy head branch name to clipboard

+116-36

Conversation Commits6 (6)Checks Files changed

Commits

Commits on Jan 24, 2025

specific rounding for UI updating
alex-Arc
committed
only update clock after 1sec where not ther updates ocurred
alex-Arc
committed
rearange update logic
alex-Arc
committed
getShouldTimerUpdate takse MaybeNumber
alex-Arc
committed
fixup! rearange update logic
alex-Arc
committed
batch updates in client
alex-Arc
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.