Skip to content

[Spec] Relay next_draft_input via GenerationBatchResult; unify scheduler install#24862

Open
hnyls2002 wants to merge 10 commits into
lsyin/spec-pr2from
lsyin/spec-pr3
Open

[Spec] Relay next_draft_input via GenerationBatchResult; unify scheduler install#24862
hnyls2002 wants to merge 10 commits into
lsyin/spec-pr2from
lsyin/spec-pr3

Conversation

@hnyls2002
Copy link
Copy Markdown
Collaborator

Summary

Stacks on #24860. Unifies the cross-iteration spec_info install across V1, V2, and Frozen KV MTP workers via GenerationBatchResult.next_draft_input.

  • Pre-PR: V1 worker mutates batch.spec_info = next_draft_input directly; V2 has its own scheduler-side install gated by is_spec_v2; Frozen does worker-side install. 3 different patterns.
  • After: every worker returns next_draft_input via GenerationBatchResult. Scheduler installs from batch_result.next_draft_input in one place.

Other cleanups (move install of batch.spec_info from prepare_* methods to the caller, drop dead check_forward_draft_extend_after_decode, rename V2 sampleverify_v2, lift V1 idle-extend swap to caller).

Test plan

  • All EAGLE V1 / V2 / Multi-layer / Frozen KV MTP suites (covers all relay paths)

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

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.

1 participant