ec704e4e2e
- setup.sh: GENESIS_PIN now defaults to commit bf667c7 (Genesis HEAD as of 2026-04-27, semver "v7.54"). This is the exact tree our published TPS numbers were measured against; tagged v7.51-stable was one minor older but came up first because the SHA isn't durable. Switch to commit pin removes the doc-vs-runtime mismatch. Clone strategy adjusted since --branch + --depth 1 doesn't accept SHAs. - .env.example: documents MODEL_DIR / HF_TOKEN / CUDA_VISIBLE_DEVICES / MEM_UTIL / MAX_MODEL_LEN / GENESIS_PIN / SKIP_GENESIS / URL / WARMUPS / RUNS with the same defaults the composes ship. Pure opt-in. - .github/ISSUE_TEMPLATE/: bug-report.yml requires docker logs --tail 100, verify-full.sh output, nvidia-smi, GPU config, compose variant, repo commit. numbers-from-your-rig.yml structures cross-rig TPS contributions with rig spec, bench output, VRAM, max ctx, and notes. config.yml routes Q&A to Discussions. - .gitignore: drop trailing slash on genesis pattern so it also ignores local symlinks that some of us point at out-of-tree clones. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
114 lines
3.5 KiB
YAML
114 lines
3.5 KiB
YAML
name: Bug report
|
||
description: Something isn't working — server crashes, OOM, wrong output, weird TPS regression, etc.
|
||
title: "[bug] "
|
||
labels: ["bug"]
|
||
body:
|
||
- type: markdown
|
||
attributes:
|
||
value: |
|
||
Thanks for filing a bug! The data we ask for below has saved hours
|
||
of back-and-forth on every previous report. Please don't skip the
|
||
log/`verify-full.sh`/`nvidia-smi` blocks — they're how we tell a
|
||
local-config issue from a real upstream regression.
|
||
|
||
- type: textarea
|
||
id: what-happened
|
||
attributes:
|
||
label: What happened?
|
||
description: One-paragraph summary. What did you expect, what did you see instead?
|
||
placeholder: |
|
||
I started `dual-turbo.yml` and it OOMs after ~30 seconds of prefill on a 32K
|
||
message. Expected: stable serving like the README says. Actual: the
|
||
attached log line.
|
||
validations:
|
||
required: true
|
||
|
||
- type: textarea
|
||
id: repro
|
||
attributes:
|
||
label: Steps to reproduce
|
||
description: Exact commands. The `compose up` line, the curl/openai-client request, etc.
|
||
placeholder: |
|
||
cd models/qwen3.6-27b/vllm/compose
|
||
docker compose -f docker-compose.dual-turbo.yml up -d
|
||
# then this curl request:
|
||
curl -s http://localhost:8020/v1/chat/completions -d '...'
|
||
render: bash
|
||
validations:
|
||
required: true
|
||
|
||
- type: textarea
|
||
id: docker-logs
|
||
attributes:
|
||
label: docker logs (last 100 lines)
|
||
description: |
|
||
Output of `docker logs --tail 100 <container-name> 2>&1`. The container
|
||
name is the `container_name:` field in the compose file you're running.
|
||
placeholder: |
|
||
docker logs --tail 100 vllm-qwen36-27b 2>&1
|
||
# paste the output here
|
||
render: text
|
||
validations:
|
||
required: true
|
||
|
||
- type: textarea
|
||
id: verify-full
|
||
attributes:
|
||
label: verify-full.sh output
|
||
description: |
|
||
Run `bash scripts/verify-full.sh` (or `verify-stress.sh` if that's
|
||
what's failing) against your running container and paste the full output.
|
||
This tells us which check fails on your rig vs. ours.
|
||
placeholder: |
|
||
bash scripts/verify-full.sh
|
||
# paste full output
|
||
render: text
|
||
validations:
|
||
required: true
|
||
|
||
- type: textarea
|
||
id: nvidia-smi
|
||
attributes:
|
||
label: nvidia-smi output
|
||
description: |
|
||
`nvidia-smi` output captured while the container is running. We need to
|
||
see VRAM use per card, driver version, and CUDA version.
|
||
placeholder: |
|
||
nvidia-smi
|
||
# paste full output
|
||
render: text
|
||
validations:
|
||
required: true
|
||
|
||
- type: input
|
||
id: gpu-count
|
||
attributes:
|
||
label: GPU configuration
|
||
placeholder: "1× RTX 3090, or 2× RTX 3090 (PCIe, no NVLink), etc."
|
||
validations:
|
||
required: true
|
||
|
||
- type: input
|
||
id: compose-variant
|
||
attributes:
|
||
label: Compose variant
|
||
description: Which `docker-compose.*.yml` file are you running?
|
||
placeholder: "docker-compose.yml (default 48K) / dual-turbo.yml / long-text.yml / ..."
|
||
validations:
|
||
required: true
|
||
|
||
- type: input
|
||
id: commit
|
||
attributes:
|
||
label: club-3090 commit
|
||
description: Output of `git -C /path/to/club-3090 rev-parse --short HEAD`.
|
||
placeholder: "e.g. 5060e22"
|
||
validations:
|
||
required: true
|
||
|
||
- type: textarea
|
||
id: extras
|
||
attributes:
|
||
label: Anything else?
|
||
description: Custom environment overrides (`.env`), non-default `MEM_UTIL`, distro/kernel oddities, anything that might matter.
|