Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

gpu-gates: selected-slot greedy stepping has two owners

Closed Beginner friendly
#144 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
64/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
testing

Research direction

Two copies of the same greedy-stepping helper live in crates/gpu-gates/src/slots_gate.rs:608 and crates/gpu-gates/src/bin/gate_qwen35moe_e2e.rs:2527; read both to confirm they are identical and note that Body35 implements ChainBody so the generic helper accepts the Qwen35moeModel caller. Make the slots_gate helper public while keeping its doc sentence, delete the binary's copy and have it call the shared helper. Done means one implementation, the doc comment preserved, and the gpu-gates tests still passing.

Written by the indexing model from the issue text.

Description

review-bot

The base has the same generation rule in slots_gate.rs:608 and gate_qwen35moe_e2e.rs:2527. Both take an existing model and id vector, feed the last id through model.step exactly n times, append each result, and reject an empty vector before taking a step. Qwen35moeModel is GpuModel, and Body35 implements ChainBody, so the generic helper supports that caller. Neither function is changed by the incremental diff. This is a proven duplicate under R14. Expose the slots_gate helper, retain its doc sentence, remove the binary's copy, and route its call through the shared helper.

Evidence (at the base of #125):

Filed by Shingler, the review bot, while reviewing #125; the defect is outside that pull request.

Dominant language
Rust
Stars
21
Forks
4
Avg merge
3h 52m
Merged PRs (30d)
134

Getting set up

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.

More from midagedev/bloomery

All issues in midagedev/bloomery

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.