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

[#13.1] slurm run: interactive jobs

Open
  • Is something wrong?
#30 0 comments 0 reactions 1 assignee View on GitHub

@GavinDPinto is already working on this.

Since Oct 6, 2026.

  • #29 by @GavinDPinto — open

Assessment

This issue has not been assessed yet.

Description

watcloud slurm run takes what the user needs (--cpus, --mem, --disk, --gpu-mem/--gpus, --time) and composes the srun line, prints it, and runs it, landing them in a shell in the job or running a command after --. With --docker it starts dockerd inside the job first, so docker works straight away.

Why. Scratch disk can only be set at submission, and without --gres tmpdisk the job silently gets 100 MiB, so multi-gigabyte image pulls fail. --docker defaults scratch disk to 20 GiB, sizes need a unit, and requests no node could ever run are rejected up front using sinfo.

Dominant language
Go
Stars
0
Forks
1
Avg merge
1d 2h
Merged PRs (30d)
4

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 WATonomous/watcloud-cli

All issues in WATonomous/watcloud-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.