Skip to main content
Search

# Conflict Detection

2 related articles

Subscribe to updates
  1. Multi-conflict detection stops at two parallel branches: the merge loop's checks are now precomputed too, averaging 1.21x on two cores

    Diagnosis of constraint systems needs several minimal conflicts at once, and MergeXplain returns multiple conflicts from one decomposition, but only its two recursive branches had been run in parallel while the merge loop that eliminates boundary-spanning conflicts stayed sequential. ParallelMergeXplain forks the recursion up to a bounded depth and replaces every GetConflict call in the merge loop with a speculative, QXGen-lookahead parallel version. On a 2-core machine it reached a mean wall-clock speed-up of 1.21x (std. 0.20) across all configurations with non-trivial checks, and 1.531x for par full at p=2 on the real SATLIB uf50-218 instance, returning results identical to sequential MergeXplain.

  2. arXiv

    Treating parallel coding-agent coordination as scheduling: NP-Bench lifts clean integration from 1/9 to 9/9 and rescues a live breaking contract change from 0.00 to 1.00

    The authors reframe coordination among parallel coding agents as a scheduling problem: before agents start, partition work into disjoint scopes from each item's declared scope and order merges along the producer-consumer dependency graph; they implement this planner in Nerveplane and evaluate it with NP-Bench, a three-arm benchmark grounded in a real git merge, where deterministic clean-integration success rises from 1/9 to 9/9 and merge conflicts fall from 13 to 0, and a live breaking contract change rises from 0.00 to 1.00 on a frontier model and 0.60 on a small one.

You’re all caught up