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

[#13.2] slurm run: --batch mode

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

@GavinDPinto is already working on this.

Since Oct 6, 2026.

Assessment

This issue has not been assessed yet.

Description

watcloud slurm run --batch ... -- <command or script> submits with sbatch instead of srun, reusing the same flags and checks. It prints the job ID and output file, and suggests watcloud subscription <id> for a notification when the job ends.

Why. compute_dense only accepts batch jobs, and long jobs belong in batch rather than interactive sessions. Getting the request right matters even more here, because a batch job that fails does so hours later, with nobody watching.

Approach. Pass the command with --wrap, or a script file as the script itself (command-line flags override #SBATCH lines). Read the job ID with --parsable. With --batch, allow compute_dense, drop the 6-hour interactive warning, allow submitting from inside a job, and warn loudly (or require --time) when no time limit is given, since the default is 30 min.

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.