Skip to content

fix(turboquant): supersede stale dependency bump#11064

Open
localai-org-maint-bot wants to merge 2 commits into
masterfrom
fix/turboquant-bump-supersede-10235
Open

fix(turboquant): supersede stale dependency bump#11064
localai-org-maint-bot wants to merge 2 commits into
masterfrom
fix/turboquant-bump-supersede-10235

Conversation

@localai-org-maint-bot

Copy link
Copy Markdown
Collaborator

Supersedes #10235 as requested by @mudler.

This carries the TurboQuant update to c26cbdffcf6fc9b7430cd6b117757e9a3f70b7ea and refreshes the HIP compatibility patch for that exact revision. The fork now includes the HIP/MUSA-safe peer-copy path, so that obsolete hunk is removed; the still-required event-creation compatibility hunk is retained at its new location.

Verification:

  • cloned TheTom/llama-cpp-turboquant at the exact pinned revision
  • git apply --check backend/cpp/turboquant/patches/*.patch
  • apply-patches.sh applied the complete patch series cleanly
  • confirmed the resulting source uses cudaEventCreateWithFlags(..., cudaEventDisableTiming)
  • git diff --check

The original PR head is fork-owned and could not accept the patch refresh directly.

mudler and others added 2 commits July 23, 2026 00:01
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
The updated fork now carries its own HIP-safe peer-copy path, so the old hunk no longer applies. Keep only the event-creation compatibility change that the fork still needs.

Assisted-by: Codex:gpt-5 [Codex]
@localai-org-maint-bot

Copy link
Copy Markdown
Collaborator Author

@mudler the superseding PR is open and the code checks are running, but DCO is ACTION_REQUIRED on the carried automated bump commit. Per the repository AI/DCO policy I cannot add or forge a human Signed-off-by; this needs your attestation or maintainer-side handling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants