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

Follow-up to #6661: Reboot sync: a watch fault after activity creation must report the import still running

Closed
  • Is something wrong?
#6,753 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #6661 by @rbuergi — merged

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
40/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
backend

Research direction

Start from the reboot sync code that calls onActivityCreated and the catch around the terminal-status watch, where StillRunning is set to null. Trace how Sequence decides to start the next import, and read the pull request #6661 discussion for the intended behaviour. Write a failing test where the watch faults after activity creation and expect StillRunning to be returned, then make the fix. Done when that test passes and pre-creation failures still let the sequence continue.

Written by the indexing model from the issue text.

Description

bug sev:M

Follow-up to #6661 (review findings deferred from that pull request; Refs #6661).

  • If the terminal-status watch faults after onActivityCreated, the catch reports StillRunning = null and Sequence starts the next import while the first may still write. Keep the created activity path and return it as still running for every post-creation watch failure; only pre-creation failures may let the sequence continue.

These are automated-review findings, assessed from the diff and not reproduced; each needs a failing test before its fix. Deferred from the PR because CI is saturated and none of them is a security hole, data loss or a broken build/test.

Dominant language
C#
Stars
12
Forks
5
Avg merge
5h 44m
Merged PRs (30d)
968

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 Systemorph/MeshWeaver

All issues in Systemorph/MeshWeaver

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.