feat: upstream TurboQuant watch tool and report (closes #15)
All checks were successful
Smoke Test / smoke (pull_request) Successful in 34s

Monitoring tool for tracking when TurboQuant lands in upstream
llama.cpp and Ollama. Checks GitHub PRs/issues for TurboQuant,
PolarQuant, QJL mentions, checks Ollama releases, and compares
fork freshness against upstream.

scripts/upstream_watch.py — Automated monitoring:
  - Search llama.cpp/ggml/ollama for TurboQuant keywords
  - Check Ollama releases for KV cache mentions
  - Compare fork commit age vs upstream
  - Generate report or JSON output
  - Run: python3 scripts/upstream_watch.py --since 30d

docs/upstream-watch-report.md — Current status:
  - TurboQuant has NOT landed upstream yet
  - Fork is CURRENT with upstream llama.cpp
  - Continue using TheTom/llama-cpp-turboquant fork
This commit is contained in:
Alexander Whitestone
2026-04-14 22:11:12 -04:00
parent 7a7ce0e652
commit b76312b024
4 changed files with 246 additions and 0 deletions

View File

@@ -0,0 +1,21 @@
# TurboQuant Upstream Watch Report
Generated: 2026-04-15 02:07 UTC
Monitoring since: 2026-03-16
## Upstream Landing Status
**No TurboQuant/PolarQuant/QJL mentions found upstream.**
TurboQuant has NOT landed in upstream llama.cpp yet.
## Fork Status
- **Upstream (llama.cpp):** 5d14e5d1 — hexagon: optimization for HMX mat_mul (#21554)
- **Fork (turboquant):** 45f8a066 — Merge: ci: fix turbo build + test failures (#66)
- **Fork freshness:** CURRENT
## Errors
- turboquant OR polarquant OR qjl: HTTP Error 422: Unprocessable Entity
- kv cache type: HTTP Error 422: Unprocessable Entity
- ggml_type: Remote end closed connection without response
## Recommendation
No upstream TurboQuant support detected. Continue using fork. Re-check weekly.