Skip to content

ComponentCatalog logging errors #975

Closed

Description

@justinormont

System information

  • OS version/distro: OSX 10.12
  • .NET Version (eg., dotnet --info): .NET Core SDK 2.1.401

Issue

When running a simple showSchema command, dotnet ./bin/AnyCPU.Release/Microsoft.ML.Console/netcoreapp2.0/MML.dll showSchema data=test/data/breast-cancer.txt, as taken from #593 (comment), many errors are displayed.

Output:

CacheClassesFromAssembly: can't map name ModuleGenerator to ModuleGenerator, already mapped to ModuleGenerator
CacheClassesFromAssembly: can't map name Module to ModuleGenerator, already mapped to ModuleGenerator
CacheClassesFromAssembly: can't map name CrossValidationBinaryMacro to Void, already mapped to Void
CacheClassesFromAssembly: can't map name CrossValidationMacro to Void, already mapped to Void
CacheClassesFromAssembly: can't map name CVSplit to Void, already mapped to Void
CacheClassesFromAssembly: can't map name DataViewReference to Void, already mapped to Void
CacheClassesFromAssembly: can't map name FeatureCombiner to Void, already mapped to Void
CacheClassesFromAssembly: can't map name ImportTextData to Void, already mapped to Void
CacheClassesFromAssembly: can't map name ExecGraph to ExecuteGraphCommand, already mapped to ExecuteGraphCommand
CacheClassesFromAssembly: can't map name ModelOperations to Void, already mapped to Void
CacheClassesFromAssembly: can't map name OneVersusAllMacro to Void, already mapped to Void
CacheClassesFromAssembly: can't map name TrainTestBinaryMacro to Void, already mapped to Void
CacheClassesFromAssembly: can't map name TrainTestMacro to Void, already mapped to Void
CacheClassesFromAssembly: can't map name TrainTestSplit to Void, already mapped to Void
CacheClassesFromAssembly: can't map name CSGenerator to CSharpApiGenerator, already mapped to CSharpApiGenerator
CacheClassesFromAssembly: can't map name CS to CSharpApiGenerator, already mapped to CSharpApiGenerator
2 columns:
  Label: R4
  Features: Vec<R4, 9>

This error is logged within the ComponentCatalog:

Console.Error.WriteLine(
"CacheClassesFromAssembly: can't map name {0} to {1}, already mapped to {2}",
name, info.Type.Name, infoCur.Type.Name);

Activity

  1. eerhardt commented on Sep 22, 2018

    @eerhardt
    Member

    Justin, can you try deleting your bin directory and rebuilding from the root again? We renamed Microsoft.ML to Microsoft.ML.Legacy recently. And I believe you have both assemblies in your bin directory causing the duplicate type error.
    I saw a similar issue myself locally.

  2. justinormont commented on Sep 25, 2018

    @justinormont
    ContributorAuthor

    @eerhardt: Exactly correct.

    After running ./build.sh -CleanAllProjects and ./build.sh -Release, the errors are gone:

    $ dotnet ./bin/AnyCPU.Release/Microsoft.ML.Console/netcoreapp2.0/MML.dll showSchema data=test/data/breast-cancer.txt
    2 columns:
      Label: R4
      Features: Vec<R4, 9>
  3. ghost locked as resolved and limited conversation to collaborators on Mar 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

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