Update llama.cpp to b10093 - #518
Conversation
b8941 -> b10093 (Tom's requested target). Source mirrored to
gs://minimal-staging-archives/ggml-org/llama.cpp/b10093.tar.gz.
The runner aborted this update on a pkgscan Critical — three `__import__(`
findings in the new conversion/__init__.py. VERIFIED false positive: they
are a plugin loader importing sibling modules by allowlisted name
(`__import__(f"conversion.{module_name}")`) to fire @ModelBase.register()
decorators — the conversion/ package refactor, benign. The pkgscan tool
is fixed to demote a static/allowlist __import__ (pm#577); a decoded
target stays gated. Re-scanned clean with that fix (0 gating findings).
Recency: b10093 is ~7h old at cut time — Medium (6-12h), which does NOT
gate the mirror (only >= High does). The newer b10094/b10098/b10099 are
inside the <6h window and would be withheld — Tom's b10093 is the newest
eligible build, exactly what the freshness picker now surfaces.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 32 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Update llama.cpp
b8941→b10093Source:
github:ggml-org/llama.cpp:tagRelease: https://github.com/ggml-org/llama.cpp/releases/tag/b10093
Changelog: ggml-org/llama.cpp@b8941...b10093
Released: ~9 hours ago
Pkgscan (Layer-1 attack detection)
Scanned the
b8941 → b10093source diff. No gating (Critical/High) findings.conversion/__init__.py:330__import__(conversion/__init__.py:339__import__(conversion/__init__.py:351__import__(The three
__import__(f"conversion.{module_name}")calls import sibling modules by allowlisted name to fire@ModelBase.register()decorators — the newconversion/package's plugin loader, not obfuscated execution. pkgmgr's scanner now demotes a static/allowlist__import__to Info while keeping a computed/decoded target gated (gominimal/pkgmgr-rs#577).Changes
b8941b10093fed02e5a…6a142f90…Source mirrored to
gs://minimal-staging-archives/ggml-org/llama.cpp/b10093.tar.gz(verified).Why b10093 and not the latest
b10093 is the newest build outside the recency dwell window: b10099 (25 min), b10098 (3.8h), b10094 (5.5h) are all <6h old and would have their mirror write withheld. b10093 (~9h, Medium) ships. This is what the freshness picker now surfaces in the
/pkgs upgrademodal.Merge gate: build + tests must pass, AND a separate human reviewer's approval — the bot only cuts the PR.
🤖 Generated with Claude Code