OpenFn / OpenFn/lightning

Handle final status for parallel runs

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

Nobody has claimed this yet.

Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

User story

We need to think about how we update the final status of parallel runs. See screenshots below for context - the final status if showing success, when one of the parallel runs failed.

Screenshot 2023-05-02 at 09.03.17.png

Screenshot 2023-05-02 at 09.03.00.png

Details
Implementation notes
Release notes
User acceptance criteria

Contributor guide

No contributing guide indexed for this repository

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

No files, tests, or entry points are named. Start by reviewing the screenshots and locating the code that computes final status for parallel runs; done should mean a failed parallel run is reflected in the displayed final status.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.