Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Calculation summary: the job's allocation and how much of it is left (projinfo / Slurm)

未关闭
#613 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
c, linux

调研方向

Start by reading the calculation summary's Launcher block and the shared SSH connection work referenced in #487 and #599; then review #541 for how accounts are stored per allocation. Identify the machine registration path for the allocation command and how remote commands are cached. Done means the summary can show the allocation, remaining core-hours, and read time, while missing or failed commands display nothing; the issue calls for design review of the remote-shell behavior.

由索引模型根据 Issue 内容生成。

描述

Andy 2026-10-27: on a cluster with a limited allocation, the calculation summary's Launcher block (Machine, Processors, Start Date, Comp. Date) should show the allocation the job runs under and how much of it is left.

  • Allocation: the account/project the job was submitted with (the Slurm --account, as stored at launch).
  • Left: core-hours used / allocated, from the site's own tool where there is one (HPC2N/NAISS: projinfo), else Slurm (sshare -A <account> / sreport), set per machine in Register Machines ("Allocation command", empty = not shown).
  • Read over the machine's shared ssh connection (#487/#599), no new login; at most every 15 min per machine and account, cached; shown with when it was read ("checked 10:20"). A failed or missing command shows nothing rather than an error.
  • Goes with #541 (several allocations on one compute machine), which stores the account per allocation.

Remote-shell code: design review before the change (no extra prompts, nothing run on a machine that has no allocation command).

主要语言
C
星标
10
派生
8
平均合并
1 小时 45 分钟
30 天内合并 PR
5

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

FriendsofECCE/ECCE 的其他 Issue

查看 FriendsofECCE/ECCE 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。