NotASithLord / NotASithLord/peerd
Local WebGPU generation can start after Stop during host startup
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 410
- Forks
- 45
- Avg merge
- 11d 5h
- Merged PRs (30d)
- 1
Description
Problem
Stop can arrive while the offscreen Local WebGPU host is starting. The abort message reaches a host that has no generation controller yet. The service worker can then send the Generate command after startup without another signal check.
Effect
A stopped generation can start late. It holds the exclusive local generation lease until its token budget ends. Later local turns can remain blocked.
Expected
An already stopped call must settle before host startup. Stop during startup must settle the stream and prevent the late Generate command. The provider must report the turn as aborted.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the offscreen Local WebGPU host startup, Stop handling, service worker Generate dispatch, and provider abort path described in the issue. Verify that an already-stopped call settles before startup, Stop during startup prevents Generate and settles the stream, and the provider reports the turn as aborted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ai
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100