question(sync): isolate enrolled-repair writer blocking in a reproducible fixture
Maintainers usually reply within 1 day
@dnlrsls is already working on this.
Since Oct 16, 2026.
Assessment
This issue has not been assessed yet.
Description
Question
Can the writer-blocking mechanism reported in #1896 be reproduced with a small synthetic fixture and bounded execution, without copying a user database or waiting hours?
Why does this need issue tracking?
#1896 includes both an incident and a potentially substantial transaction redesign. This sub-issue is one evidence-producing unit only. Its result will bound a later fix; it must not silently expand into implementing that fix.
Affected Area
Sync (multi-instance)
Additional Context
Parent: #1896. Reported frames include repairEnrolledProjectSyncMutations and backfillProjectSyncMutationsTx; this is not a new local reproduction. Uses the tracked-question form fields; this gh version forbids combining --template and --body.
Acceptance:
- Pin the tested commit, platform and actual repair entry point.
- Use synthetic data and isolated state, with a documented runner timeout and cleanup.
- Exercise the real repair path and an independent writer; record completion/error and transaction synchronization or timing evidence.
- Deliver a minimal repeatable command/fixture. If not reproducible within the bound, record the inconclusive result and missing discriminator, not a confirmation.
- State the invariant for a subsequent regression and the remaining fix decision.
Non-goals: transaction redesign, migrations, production-data access, full autosync refactoring, CI Trust, releases. No production fix is required to close this investigation with a supported verdict.
- Dominant language
- Go
- Stars
- 7.1k
- Forks
- 729
- Avg merge
- 10h 43m
- Merged PRs (30d)
- 332
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 Gentleman-Programming/engram
-
status:needs-review type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Gentleman-Programming/engram#1687 ·
Maintainers usually reply within 1 day
-
priority:medium status:needs-review type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Gentleman-Programming/engram#863 · 1 comment ·
Maintainers usually reply within 1 day
-
status:needs-review type:bug
Difficulty 4/5 3-5 days Newbie friendliness 12/100
Gentleman-Programming/engram#1912 ·
Maintainers usually reply within 1 day
-
status:needs-review type:bug
Difficulty 5/5 Over a week Newbie friendliness 15/100
Gentleman-Programming/engram#1911 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
Gentleman-Programming/engram#1909 · 1 comment ·
Maintainers usually reply within 1 day
All issues in Gentleman-Programming/engram
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:session-state issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openclaw/wacli#503 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 81/100
apache/rocketmq-dashboard#6895 ·
Maintainers usually reply within 3 days
-
agent-butler-finding chore
Difficulty 1/5 Under an hour Newbie friendliness 88/100
jordansmall/spindrift#5466 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
open-telemetry/opentelemetry-go-compile-instrumentation#1507 ·
Maintainers usually reply within 3 days