Skip to content

testSearchPackagesListsPackagesForExistingProject fails if MCP not loaded "directly" #136

Description

@NicolasAnquetil

I loaded MCP through dependency in another project (NicolasAnquetil/MooseMCP)
as a result, testSearchPackagesListsPackagesForExistingProject was failing

Claude identified the error as:

  1. MCPPackageScopeQuery>>resolvedProjectsNamed: looks up 'MCP' in projectsByName, which is built from projectRegistrations
  2. that method filters MetacelloProjectRegistration registry registrations down to only those where loadedInImage is true.
  3. 'MCP' loadedInImage flag is false. That flag only gets flipped to true inside MetacelloScriptEngine's actual load: path ; it's never set when a project's code is just present/loaded another way (e.g. via Iceberg checkout in an image).

After reloading MCP "directly" through metacello (install baseline "default"), the test passes

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions