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

Job Launchpad may need a protection against LFN sandbox

Open
#723 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend, security

Research direction

Read JobLaunchpadHandler.py around line 201 and JobWrapper.py around line 1127 to trace how LFNs become sandbox downloads. Compare where file counts, volume, or available disk space could be checked. Done means a directory LFN cannot fill a worker-node disk without being rejected or bounded by an explicit protection.

Written by the indexing model from the issue text.

Description

We had a case where

  1. A user used the DIRAC JobLaunchpad WebApp specifying a LFN
  2. The "LFN" specified was not a file, but a directory
  3. The job started downloading files under the directory, filling up the WN disk
  4. The site found the problem and closed the WN, then contacted us

JobLaunchpadHandler simply adds the specified LFNs to JDL
https://github.com/DIRACGrid/WebAppDIRAC/blob/9948d0ef327368ed1e502f41e029f91de3af121d/src/WebAppDIRAC/WebApp/handler/JobLaunchpadHandler.py#L201

JobWrapper simply passes the sandbox files with "LFN:" to DMS getFile
https://github.com/DIRACGrid/DIRAC/blob/fdfd3a4802a5543369d307cbbb3c0781f2f14219/src/DIRAC/WorkloadManagementSystem/JobWrapper/JobWrapper.py#L1127

Can there be some kind of protection to avoid this?
Preferably in JobLaunchpad, with the number of files, or with the total volume?
If that is difficult in the WebApp, then in JobWrapper where it can tell the disk space and the volume of the sandbox?

Dominant language
JavaScript
Stars
8
Forks
42
PR merge metrics
No merged PRs in 30d

Getting set up

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.

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.