llnl / llnl/maestrowf

lock files in /tmp

Open
#87 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Good First Issue
Dominant language
Python
Stars
161
Forks
49
PR merge metrics
No merged PRs in 30d

Description

Just an idea, but maybe the lock files could be stored in /tmp? This way it's a few fewer inodes used in our file systems.

Contributor guide

Open the 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.

Research direction

The issue names no files, tests, or entry points. First locate where lock-file storage is configured and used, then check whether /tmp is suitable for both local and supercomputer workflows. Done means the storage behavior is defined and the affected cases are covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.