Skip to content

Use outgoing dependencies for the default providers query - #3

Open
deem0n wants to merge 1 commit into
developmentfrom
fix-default-providers-query
Open

deem0n wants to merge 1 commit into
developmentfrom
fix-default-providers-query

Conversation

@deem0n

@deem0n deem0n commented Sep 20, 2026 •

Copy link
Copy Markdown
Owner

The application default providers query used allClients, so a newly opened Butterfly map could show incoming clients on both sides. It now uses allProviders; the default clients query remains unchanged.

The regression test builds a real client -> central -> provider invocation chain and checks the two default queries independently, avoiding a symmetric fixture that would conceal the bug.

Revalidated for this milestone in an isolated Pharo 13 / Moose 13 image: 50 passed, 2 skipped, 0 failures/errors across MiApplicationTest, MiButterflyMapModelTest and MiButterflyMapBrowserTest.

Addresses deem0n/FAMIXNGSQL#23. This is a fork-targeted review of existing commit c7d7e46, already proposed upstream in moosetechnology#1659. It does not create a duplicate upstream implementation. The v3 integration image must contain the fix before the issue is closed.

Updated CI evidence

Full fork CI test job passed: https://github.com/deem0n/MooseIDE/actions/runs/35536994921. Actions is now enabled and the fork-specific MOOSE_PHARO_VERSIONS repository variable supplies the Pharo 13 matrix; earlier notes about unavailable fork CI are superseded. Combined SQL qualification is tracked in deem0n/FAMIXNGSQL#32. Release acceptance stays open until reviews and final integrated checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant