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

[Bug] ParallelSplit reverses parent and child job relationships

Open Beginner friendly
#4,672 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@iancooper is already working on this.

Since Oct 30, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
backend

Research direction

Read Steps.cs around ParallelSplit.ExecuteAsync and Job.cs around AddChildJob to confirm how parent and child IDs are assigned. Add regression coverage for a two-branch split and a nested split, checking that each branch points to the original job and its parent hierarchy stays unchanged. Done when those assertions pass.

Written by the indexing model from the issue text.

Description

1 - Up Next Workflows (Future Feature)

Confirmed behavior

At c4e128c4f09c068e930a8165cb37f3880840edbe, ParallelSplit.ExecuteAsync (Steps.cs:200–203) creates childJob and calls childJob.AddChildJob(Job).

Job.AddChildJob (Job.cs:179–182) sets its argument ParentId to the receiver Id and adds the argument to the receiver children dictionary. The call is reversed: the original parent receives the new child ID as its ParentId, while the new child keeps ParentId=null and records the original parent as its child. With multiple branches, the original parent ParentId is overwritten by the last child ID.

This is a direct source-level verification of argument/receiver values and assignments; no runtime test execution is claimed. Search for ParallelSplit parent found no duplicate.

Expected

Call Job.AddChildJob(childJob), so every spawned branch has the original job ID as ParentId, the parent retains its own ParentId, and the parent tracks its branches.

Regression coverage

Split a job into two branches. Inspect the queued jobs and assert each ParentId equals the original job ID and the original ParentId is unchanged. Include a nested split to preserve the original parent hierarchy.

Dominant language
C#
Stars
2.5k
Forks
301
Avg merge
1d 2h
Merged PRs (30d)
87

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from BrighterCommand/Brighter

All issues in BrighterCommand/Brighter

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.