plan 레코드: 호스트에 고정된 layer와 그 이유(host_only_reason)가 출력에 없음
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- machine-learning
Research direction
Start with PlanInputs::host_only() and the host-only reason logic in crates/model/src/arch/qwen35moe/place.rs (lines 127-139 and 552-569), then see how PLAN's n_l is written in crates/gpu-gates/src/record.rs around line 1010. Choose between adding the layer and reason to PLAN or creating a new record kind, as the issue says new meanings should get a new kind. Run just mac-check and just mac-lint; the maintainer runs just records-refresh. Done when plan output shows which layers stay on the host and why.
Written by the indexing model from the issue text.
Description
카드에 expert kernel이 없는 타입의 routed expert는 그 layer 전체가 호스트에 남습니다(host_only_reason). 그런데 이 이유가 plan 레코드에 없어서, 그런 layer는 plan 출력에 n_l 0으로만 보입니다. 사용자는 왜 카드에 안 올라갔는지 알 수 없습니다. PlanInputs::host_only()는 지금 테스트에서만 읽힙니다.
PLAN 레코드에 호스트 고정 layer와 이유를 싣거나, 새 레코드 kind를 하나 만들어 주세요(새 의미는 새 kind가 원칙입니다).
- 파일:
crates/model/src/arch/qwen35moe/place.rs:127-139, 552-569,crates/gpu-gates/src/record.rs:1010(PLAN의n_l) - 검증:
just mac-check,just mac-lint. 레코드가 바뀌면just records-refresh(박스)가 필요해서 메인테이너가 돌립니다.
처음이시면 CONTRIBUTING.ko.md부터 봐 주세요. 작업을 맡으실 분은 댓글로 알려 주세요.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 4
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 134
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from midagedev/bloomery
-
review-bot
Difficulty 2/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
hidden_ref: invalid numeric options silently select defaultsPossibly taken @midagedev claimed this today. Openreview-bot
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
review-bot
Difficulty 3/5 1-2 days Newbie friendliness 56/100
midagedev/bloomery#214 · 1 comment ·
Maintainers usually reply within 1 day
All issues in midagedev/bloomery
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
ActivityWatch/aw-notify-rs#47 · 1 comment ·
-
`inverse()` of a controlled `CUGate` drops the phase parameter γPossibly taken @rupasri118 claimed this today. Openbug mod: circuit
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Qiskit/qiskit#17223 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 2 days
-
agent:triaged bug bughunt pm:bundler priority:p1
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
SocketDev/socket-patch#1573 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
bytecodealliance/rustix#1706 · 1 comment ·
Maintainers usually reply within 11 days