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

T29 — Non-uniform batch (`BatchedDirectSolver`)

Open
  • Is something wrong?
#116 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Domain
backend

Research direction

The scope lives in the T29 section of TASKS.md on main, not in this issue, so read that section and STATE.md §8 first. Do not start until #115 (T28) is merged, and check for the on-hold label. The work covers block-diagonal packing and a forest schedule, with test_nonuniform_batch_cudss.jl ported. Done means the listed tests pass on the KA CPU backend and the CUDA runner, with Run tests and Aqua green.

Written by the indexing model from the issue text.

Description

task

Task T29 of TASKS.md — milestone M10 — Non-uniform batch. (Was T22 until the 2026-10-09 renumbering, see STATE.md §8; not on MadNLP's path, so it follows the performance tasks.)

Depends on: #115 (T28) must be merged first; tasks are strictly sequential.

Summary (from TASKS.md): block-diagonal packing, forest schedule; test_nonuniform_batch_cudss.jl ported.

Scope and deliverables: the section T29 of TASKS.md on main is the single source of truth; it is not copied here so it cannot drift.

Definition of done:

  • Every test listed in the task passes on the KA CPU backend and on the CUDA self-hosted runner (Run tests and Aqua green on the PR).
  • The task's status marker in TASKS.md is set and its Report block is filled in honestly (CUDA counts come from CI).
  • A PR titled T29: … from branch task/T29-<slug> with Closes #116 in its body, reviewed by the Claude reviewer with VERDICT: APPROVE.
  • Out-of-scope bugs or follow-ups found on the way are opened as separate issues (label found-by-agent), not fixed silently.

How it starts: add the label claude:implement (the pipeline does this automatically after the previous task's PR merges; label on-hold to prevent that).

Dominant language
Julia
Stars
3
Forks
0
Avg merge
4h 1m
Merged PRs (30d)
73

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 exanauts/SparseDirectSolver.jl

All issues in exanauts/SparseDirectSolver.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.