project_6

Author SHA1 Message Date

Author	SHA1	Message	Date
muh-bot	9a7fd70150	[CRITICAL/base] Register qwen3_coder tool parser as hermes alias Without this: --tool-call-parser qwen3_coder causes api_server.py to crash with KeyError at line 537: 'invalid tool call parser: qwen3_coder' This is AFTER the --reasoning-parser crash (fixed in `b446763`) - even if argparse passes, this KeyError kills the server. Qwen3 models use Hermes-compatible tool calling format: <tool_call>{"name": "func", "arguments": {...}}</tool_call> So registering qwen3_coder -> Hermes2ProToolParser is semantically correct. This was the SECOND startup blocker preventing the benchmark task from completing. The first was --reasoning-parser (fixed). Together these explain why task_id=3905102 has been stuck at status=running for 84+ minutes. Startup sequence that was failing: 1. argparse --reasoning-parser qwen3 -> CRASH (fixed `b446763`) 2. ToolParserManager.get_tool_parser('qwen3_coder') -> KeyError (fixed NOW) 3. Qwen3_5MoeForCausalLM not in registry -> crash (fixed `08dc010`) All three must be fixed for the server to start.	2026-08-06 06:10:50 +00:00
dylanyunlon	ef6abf3dc7	[DEPLOY] Complete submission: baseline + all optimizations Adds ALL files needed for Dockerfile build: - qwen3_6_scripts/ (baseline patches + our optimizations) - vllm/ (full vllm package) - paged_attention_v2_pytorch.py (V2 with single-bmm optimization) - Dockerfile + computility-run.yaml Our optimizations vs baseline: 1. paged_attn.py: pre-gathered context KV (eliminates 194 gather calls), Triton try/fallback, V2 heuristic, threshold 32K→64K 2. paged_attention_v2_pytorch.py: fills NotImplementedError, single-bmm Phase 1 (195 launches → 3) 3. patch_enable_triton.py: HAS_TRITON=True with safety fallback 4. patch_triton_tuning.py: BLOCK=64, NUM_WARPS=4 for BI-V100 5. computility-run.yaml: gpu-memory-utilization 0.9→0.95, max-num-batched-tokens 8192→16384 This repo can now be submitted to dev.modelhub.org.cn as-is.	2026-07-30 16:06:20 +00:00

muh-bot

9a7fd70150

[CRITICAL/base] Register qwen3_coder tool parser as hermes alias

Without this: --tool-call-parser qwen3_coder causes api_server.py to crash
with KeyError at line 537: 'invalid tool call parser: qwen3_coder'
This is AFTER the --reasoning-parser crash (fixed in b446763) - even if
argparse passes, this KeyError kills the server.

Qwen3 models use Hermes-compatible tool calling format:
  <tool_call>{"name": "func", "arguments": {...}}</tool_call>
So registering qwen3_coder -> Hermes2ProToolParser is semantically correct.

This was the SECOND startup blocker preventing the benchmark task from
completing. The first was --reasoning-parser (fixed). Together these
explain why task_id=3905102 has been stuck at status=running for 84+ minutes.

Startup sequence that was failing:
  1. argparse --reasoning-parser qwen3 -> CRASH (fixed b446763)
  2. ToolParserManager.get_tool_parser('qwen3_coder') -> KeyError (fixed NOW)
  3. Qwen3_5MoeForCausalLM not in registry -> crash (fixed 08dc010)

All three must be fixed for the server to start.

2026-08-06 06:10:50 +00:00

dylanyunlon

ef6abf3dc7

[DEPLOY] Complete submission: baseline + all optimizations

Adds ALL files needed for Dockerfile build:
  - qwen3_6_scripts/ (baseline patches + our optimizations)
  - vllm/ (full vllm package)
  - paged_attention_v2_pytorch.py (V2 with single-bmm optimization)
  - Dockerfile + computility-run.yaml

Our optimizations vs baseline:
  1. paged_attn.py: pre-gathered context KV (eliminates 194 gather calls),
     Triton try/fallback, V2 heuristic, threshold 32K→64K
  2. paged_attention_v2_pytorch.py: fills NotImplementedError,
     single-bmm Phase 1 (195 launches → 3)
  3. patch_enable_triton.py: HAS_TRITON=True with safety fallback
  4. patch_triton_tuning.py: BLOCK=64, NUM_WARPS=4 for BI-V100
  5. computility-run.yaml: gpu-memory-utilization 0.9→0.95,
     max-num-batched-tokens 8192→16384

This repo can now be submitted to dev.modelhub.org.cn as-is.

2026-07-30 16:06:20 +00:00

2 Commits