mudler / mudler/vllm.cpp

#2777 deleted a recorded closed negative along with its stale preamble

Open Beginner friendly
#2,943 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
423
Forks
53
Avg merge
20h 26m
Merged PRs (30d)
310

Description

Row: GFX1100-TG200

#2777 removes this paragraph from
docs/bench-evidence/gfx1100-tg200-t2b-20260823.md:

## Session-state note (hindsight unavailable)

Hindsight memory store was returning 500s during this session, so the
campaign state is recorded here instead: T2b commit is 90f7ca064; prior
levers are 369e4b044 (merged gate_up) and 69c514a1d (quant-cache rejection);
the pointer-keyed activation-quant cache approach is UNSOUND under the
DevicePool block-recycling allocator -- do not retry it without a
content-identity signal.

The preamble is stale and worth dropping. The last sentence is a closed
negative, and it is the only place the tree records it: a recycled DevicePool
block can present a pointer the cache still believes it owns, so the approach
cannot be made correct without a content-identity signal. A recorded negative is
what stops the next session re-running the same experiment, and AGENTS.md is
explicit that evidence is not deleted to reduce context.

Fixed in the same flow: the finding is restated without the preamble.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docs/bench-evidence/gfx1100-tg200-t2b-20260823.md and read the evidence-preservation guidance in AGENTS.md. Confirm that the stale session-state preamble is removed while the closed negative about pointer-keyed caching and recycled DevicePool blocks remains recorded in the restated finding.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
85/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.