[FEAT-API Lambda]: Handle cascading Lambda effects
@martyheynbah is already working on this.
Since Jul 8, 2026.
Assessment
This issue has not been assessed yet.
Description
If a user soft deletes or archives a LCG Lamnda, this then in turn invalidates all of the hydrograph sets that used this lcg outputs and then in turn all of the eurotop lambda runs that used the hydrograph set.
- lcg lambda output archived -> hydrograph sets corrupted -> eurotop lambda corrupted
How to handle keeping old output
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from USACE/chart-docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
USACE/chart-docs#756 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
USACE/chart-docs#750 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
USACE/chart-docs#761 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
USACE/chart-docs#760 ·
-
[FEAT-API/UI]: Add ability to download hydrograph input / outputPossibly taken @noarevalo-bah claimed this 4 days ago. Open
USACE/chart-docs#759 · 1 assignee ·