Skip to content

Fail closed in DAG postprocessing - #373

Open
oshaughnessy-junior wants to merge 2 commits into
rift_O4dfrom
fix/consolidate-postprocess-path-o4d
Open

oshaughnessy-junior wants to merge 2 commits into
rift_O4dfrom
fix/consolidate-postprocess-path-o4d

Conversation

@oshaughnessy-junior

@oshaughnessy-junior oshaughnessy-junior commented Sep 21, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • resolve legacy, hyperpipeline, and NR postprocessing helpers relative to the installed wrapper, with a guarded PATH fallback
  • propagate cleaner, sort/copy, and relabel failures instead of accepting empty products
  • require nonempty composite and indexed outputs before packaging success
  • add sanitized-PATH regression coverage for missing helpers, sibling resolution, helper failures, and empty outputs

Production motivation

Calibration reruns exposed a fail-open path: util_ILEdagPostprocess.sh was invoked by absolute path, but its bare util_CleanILE.py call was absent from the worker PATH. The wrapper still returned zero and left an empty consolidated_N.composite, so failure appeared only in a later DAG POST check.

This patch preserves the newer O4d hyperpipeline and dynamic sort-key behavior. It does not hardcode any production environment path or alter DAG science configuration.

Testing

  • bash -n on both modified wrappers
  • pytest -q MonteCarloMarginalizeCode/Code/test/test_dag_postprocess_fail_closed.py (6 passed)

This is the O4d half of a coordinated O4c/O4d fix. Paired O4c PR: oshaughn#197

@oshaughnessy-junior
oshaughnessy-junior had a problem deploying to private-review-dispatch-rift September 21, 2026 09:20 — with GitHub Actions Failure

This branch had an error being deployed

1 failed deployment
private-review-dispatch-rift — f0a62f6a Deployed Sep 21, 2026 by oshaughnessy-junior via Dispatch exact RIFT PR generation #1432
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants