Follow the ex_mcp fork to b633187: owned-process close race fix - #108
Merged
Merged
Conversation
The constellation's one ex_mcp ref moves from 7222f0f5 to b6331871. Two fork commits land with it: #7 teaches OwnedProcess to treat a child that already exited as stopped during close, and #8 stops git_hooks from reinstalling itself on every mix run. #7 is the one imp needed. The {:error, :no_process} MatchError race made test/acp_imp_acp_test.exs:1628 and test/acp_local_test.exs:64 flaky in CI. Those two files ran five times in a row on this ref: 5/5 green, 57 tests and 0 failures each time. The two example projects build against the local imp in CI (IMP_PATH=../..), so their locks follow the same ref. decisions.md names the pin, so its sha moves too; the decision itself is unchanged. mix check: 54 doctests, 9 properties, 2858 tests, 0 failures, 13 skipped. mix quality.check: credo clean, mix hex.audit still red on the three cowlib 2.20.0 advisories that PR #107 fixes. Untouched here.
deepfates
force-pushed
the
claude/exmcp-bump
branch
from
September 16, 2026 00:20
ec9aace to
ce25c18
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One ex_mcp ref across kite, haven and imp (dwell inherits it through imp). It moves from
7222f0f5fa65c71988a946abe76c6b5fd5438342tob63318718d623f87a28a9723039233ca1627783b,origin/masterof thedeepfates/ex_mcpfork. kite, haven and imp get this same sha in three PRs opened together.What the fork gained
MatchErroron{:error, :no_process}. This is the one imp needed.auto_installoff).Flaky tests this addresses
test/acp_imp_acp_test.exs:1628andtest/acp_local_test.exs:64, both flaky in CI on the{:error, :no_process}MatchError race.Those two files, run five times in a row on the new ref:
5/5.
Verification
mix deps.get;grep ex_mcp mix.lockshowsb63318718d623f87a28a9723039233ca1627783b.mix check— 54 doctests, 9 properties, 2858 tests, 0 failures, 13 skipped (261 excluded).mix quality.check— credo--only warningis clean (14577 mods/funs, no issues);mix hex.auditstill exits 1 on the three cowlib 2.20.0 advisories (EEF-CVE-2026-43971,EEF-CVE-2026-43966,EEF-CVE-2026-43969). That is the known red that PR Fix the failure-campaign leak-baseline flake; bump nltk and transformers #107 fixes, it predates this change, and nothing here touches it.Also in this diff
examples/deployment/mix.lockandexamples/workspace_agent/mix.lock. Both example projects build against the local imp in CI (IMP_PATH=../..), so their locks resolve to the same ref; regenerated withmix deps.get, one line each.decisions.mdrow for the pin states it by sha, so its sha moves with it. The decision itself — one ref for all four repositories, moved only in a coordinated change — is unchanged.Not in this diff
dwell pins imp by git ref (
@imp_refin itsmix.exs) and needs bumping to imp's new main after this merges. Deliberately left out.