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

T27 — Hybrid memory / hybrid execute

Open
  • Is something wrong?
#27 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
julia
Domain
backend, performance, testing

Research direction

Start with the T27 section in TASKS.md, then read the PLAN.md sections it names and the Report blocks from previous tasks; T26 must be merged first. Run the listed tests on the KA CPU, CUDA, and AMDGPU runners, along with Aqua. Done means the required robustness and mixed-precision tests pass, TASKS.md is updated honestly, and the prescribed reviewed PR is created.

Written by the indexing model from the issue text.

Description

task

Task T27 of TASKS.md — milestone M12 — Hybrid modes. (Renamed on 2026-10-09: robustness extras moved to T28, see STATE.md §8.)

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

Summary (from TASKS.md): host-resident panels streamed per level with pinned memory; hybrid_device_memory_min; CPU-backend execution of regime A/B levels; test: a factorization under a device memory budget smaller than the factor size completes with the same solution.

Scope and deliverables: the section T27 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 T27: … from branch task/T27-<slug> with Closes #27 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
3h 2m
Merged PRs (30d)
65

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.