mirror of
https://seed.radicle.dev/rad:z4V1sjrXqjvFdnCUbxPFqd5p4DtH5.git
synced 2026-11-14 02:50:51 +08:00
Alessio Caiazza
9c790a7d1c
The hostile input tests compared elapsed time against fixed limits, so they measured the machine as well as the code. They fail on slower or loaded builders, such as the nixpkgs x86_64-linux check phase, even though rendering stays linear. Compare the CPU time of an input against one four times as long instead. Linear rendering gives about 4 and a quadratic regression about 16. CPU time is needed because a wall-clock ratio inflates under bursty load, when a short run fits between bursts and a long one does not. Rendering past the reference limit gets its own test, since the link count cannot catch a limit that stops linking but keeps rescanning. The bare reference test now puts a valid reference before the long run, so giving up is visible in the result without any timing. AI-assisted: Claude Code (claude-opus-5-5)
radicle-gui
Graphical interfaces for Radicle, a peer-to-peer code collaboration and publishing stack.
explorer/: the web explorer, deployed at radicle.network, with theradicle-httpdandradicle-searchbackends 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/.