Yorgos SaslisandDaniel Norman 8999521aa4 httpd: Keep reading node events during rescans
A rescan can take tens of minutes on permissive seeds and blocked the
event loop meanwhile. radicle-node drops a subscriber once 8192 events
are queued, so every rescan disconnected us and the events emitted
until the resubscribe were lost.

Rescans and batch reindexes now run alongside the event loop, and the
subscription reconnects on its own task. A repo that an event adds
during a rescan only gets back into the seeded cache when its batch
runs, so it can be missing for up to RADICLE_SEARCH_BATCH_SECS.

Co-authored-by: Daniel Norman <daniel@norman.life>
2026-10-29 17:17:14 +01:00
2026-10-22 14:48:27 +02:00
2026-10-29 16:27:03 +01:00
2026-10-29 16:27:03 +01:00

radicle-gui

Graphical interfaces for Radicle, a peer-to-peer code collaboration and publishing stack.

  • explorer/: the web explorer, deployed at radicle.network, with the radicle-httpd and radicle-search backends it talks to.
  • desktop/: the desktop app.
  • shared/ui/: UI components, design tokens and fonts used by both.

One npm workspace at the root holds all three: install the dependencies there, with npm ci -w explorer or npm ci -w desktop for a single app. Each app is built, tested and released on its own; see its README. The guidelines for contributing to either are in CONTRIBUTING.md, and decisions that affect the whole repository are in docs/adr/.

S
Description
Radicle web interface
Readme
201 MiB
Languages
Svelte 42%
TypeScript 32%
Rust 20.7%
JavaScript 2.1%
Shell 1.4%
Other 1.8%