[😋]
Rust · active 2025-11-21 → 2026-08-03 (UTC)
Partial coverage11,179 / 11,816 hourly files (95%) · 2 absent upstream · 634 failed, retryable2025-04-05 → 2026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
2.3K
Pushes
1.7K
Pull requests
9
Issues
98
Stars
236
Forks
33
Activity over time
Daily event counts in the loaded window
Line chart, 256 days from 2025-11-21 to 2026-08-03. Pushes: 1,726 total, peak 109 in a day. Pull requests: 9 total, peak 2 in a day. Issues: 98 total, peak 4 in a day. Comments: 146 total, peak 8 in a day. Stars: 236 total, peak 12 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| Dicklesworthstone | 1.9K | 1.7K | 0 | 110 |
| CasualDeveloper | 7 | 0 | 1 | 5 |
| blueraz0r | 5 | 0 | 0 | 1 |
| mrm007 | 4 | 0 | 0 | 2 |
| chatgpt-codex-connector[bot] | 4 | 0 | 0 | 3 |
| tomatitito | 3 | 0 | 1 | 1 |
| Jamesun921 | 3 | 0 | 0 | 1 |
| uuuser-name | 3 | 0 | 0 | 2 |
| shunkakinoki | 3 | 0 | 0 | 1 |
| jwross24 | 3 | 0 | 0 | 2 |
| Mic92 | 2 | 0 | 1 | 1 |
| voidswamp | 2 | 0 | 0 | 1 |
| LoveJazzTZ | 2 | 0 | 0 | 0 |
| 0xble | 2 | 0 | 0 | 0 |
| tha-hammer | 2 | 0 | 0 | 1 |
| carmandale | 2 | 0 | 1 | 0 |
| yusuftok | 2 | 0 | 0 | 0 |
| kr37swarm | 2 | 0 | 0 | 1 |
| amirasyraf | 1 | 0 | 0 | 0 |
| theirongolddev | 1 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#357tizerluo2026-07-25 23:43OpenCode connector double-tags local opencode.db sessions under configured remote SSH sources
- Issue#324Dicklesworthstone2026-07-11 12:49Orphaned cass-lexical-{merge,shards}.* staging dirs are never reclaimed after a crash → unbounded disk growth (410 GB in one night)
- Issue#287Dicklesworthstone2026-06-13 22:53v0.6.13: doctor/check + one-shot index refresh time out with zero robot output; stale checkpoint/quarantine makes search hang
- Issue comment#287Dicklesworthstone2026-06-13 22:53v0.6.13: doctor/check + one-shot index refresh time out with zero robot output; stale checkpoint/quarantine makes search hang
- Issue#289Dicklesworthstone2026-06-13 22:53v0.6.13: federated lexical materialization deletes the just-persisted rebuild checkpoint; every search then WARNs "lexical rebuild checkpoint missing" and the deferred repair re-runs full rebuilds without converging
- Issue comment#289Dicklesworthstone2026-06-13 22:53v0.6.13: federated lexical materialization deletes the just-persisted rebuild checkpoint; every search then WARNs "lexical rebuild checkpoint missing" and the deferred repair re-runs full rebuilds without converging
- Issue comment#289Dicklesworthstone2026-06-13 14:12v0.6.13: federated lexical materialization deletes the just-persisted rebuild checkpoint; every search then WARNs "lexical rebuild checkpoint missing" and the deferred repair re-runs full rebuilds without converging
- Issue#288blueraz0r2026-06-11 22:10Rebuild-pipeline flow-control starvation still parks on v0.6.13
- Issue comment#282Dicklesworthstone2026-06-09 19:32v0.6.10 + v0.6.11: `cass index --full` post-bulk-phase wedge at lexical staging→publish; `cass search` triggers partial recovery; only 1/8 agents ingested
- Issue#285blueraz0r2026-06-07 23:13No working recovery path for a corrupt canonical archive under v0.6.13 — the gate's own recommended recovery (`.recover` → reindex) is impossible
- Issue comment#269blueraz0r2026-06-07 23:01`watch_startup:scan_entry` rebuild-pipeline wedge on v0.6.9 — exposed after `CASS_SKIP_PREFLIGHT_CLEANUP_ORPHAN_FK_ROWS=1` clears the cass#265 wedge; classic v0.5.0-style all-threads-parked deadlock with `producer_budget_wait` accumulating
- Issue comment#284Dicklesworthstone2026-06-07 22:58ran `cargo clippy --allow-dirty --fix -- -Wclippy::use_self`
- Issue#283igouss2026-06-06 20:07v0.6.11 still pins fsqlite 0.1.5 — frankensqlite#105 FTS5 fix (now in fsqlite 0.1.7 / fts5 0.1.8) not picked up; warm search still ~8.5s
- Issue#281NeuralEmpowerment2026-06-05 23:51`cass sessions --week` is silently ignored, returns 0 sessions with no error
- Issue#275DanielsLoud2026-06-05 01:51Bug: TUI HTML export modal key hints do not reliably trigger export
- Issue#273Dicklesworthstone2026-06-04 23:49Claude Code coverage is incomplete on macOS — Desktop app stores session metadata in a separate path, and CLI bodies are auto-culled
- Issue#270Dicklesworthstone2026-06-04 23:45Per-connector watermark: a connector enabled after last_scan_ts advanced skips its pre-watermark backlog
- Issue comment#273Dicklesworthstone2026-06-03 22:48Claude Code coverage is incomplete on macOS — Desktop app stores session metadata in a separate path, and CLI bodies are auto-culled
- Issue comment#270Dicklesworthstone2026-06-03 22:48Per-connector watermark: a connector enabled after last_scan_ts advanced skips its pre-watermark backlog
- Issue comment#271Dicklesworthstone2026-06-02 01:53v0.6.9: doctor reconstructs clean higher-coverage candidate, but repair refuses promotion and lexical rebuild stalls at 695/897
- Issue#270Dicklesworthstone2026-06-01 22:23Per-connector watermark: a connector enabled after last_scan_ts advanced skips its pre-watermark backlog
- Releasegithub-actions[bot]2026-05-30 01:30v0.6.6
- Issue comment#259Dicklesworthstone2026-05-28 06:11cass index hangs forever — infinite loop in fsqlite BtCursor on a multi-level messages B-tree
- Issue comment#261JordanChoo2026-05-28 01:39Add startup FTS5 integrity check for missing/corrupt fts_messages shadow tables
- Releasegithub-actions[bot]2026-05-27 12:22v0.6.3
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 236 stars here means stars gained during the window, not the repo's star count.