Skip to content

packages/gossiplog: refactor remote clock #506

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 19, 2025

Conversation

joeltg
Copy link
Contributor

@joeltg joeltg commented Jun 19, 2025

How has this been tested?

  • CI tests pass
  • Tested with example-chat (including login, all signers, and exchanging messages)
  • Tested with @canvas-js/test-network: (optional)

Does this contain any breaking changes to external interfaces?

  • Contract interfaces
  • Core interface
  • CLI
  • Data storage formats, including IndexedDB, SQLite, or filesystem storage (will this break existing apps?)

@raykyri raykyri merged commit 121b1c5 into raymond.remote-clock Jun 19, 2025
3 checks passed
raykyri added a commit that referenced this pull request Jun 19, 2025
…#505)

* packages/gossiplog: track remote clocks

* packages/hooks: add useRemoteClock hook

* packages/hooks: formatting

* packages/gossiplog: refactor remote clock (#506)

* packages/hooks: add back disconnect event

* packages/hooks: merge useRemoteClock and useSyncStatus

* examples/forum: use progress calculated in hook

---------

Co-authored-by: Joel Gustafson <joelgustafson@protonmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants