Foundry CLI errors for unknown variant are impossible to troubleshoot

Ask the Community
1

I attempted to import an ontology into SuperRepo using the foundry cli and get this error:

DEBUG cli::errors:227: Converting Conjure error into report Error(
    "unknown variant `decimal`, expected one of `array`, `attachment`, `boolean`, `date`, `double`, `geohash`, `geoshape`, `integer`, `interfaceObject`, `long`, `marking`, `mediaReference`, `object`, `objectSet`, `objectType`, `string`, `struct`, `timestamp`, `vector`",
)
DEBUG cli::errors:289: Converting foundry service error to FoundryCliError: SerializableError {
    error_code: Internal,
    error_name: "Default:Internal",
    error_instance_id: 873c55cc-7646-4287-ae92-d06dbe97444e,
    parameters: {},
} 

FoundryServerError(
    FoundryServiceError {
        error_name: "Default:Internal",
        error_code: Internal,
        error_instance_id: "873c55cc-7646-4287-ae92-d06dbe97444e",
        parameters: {},
        backtrace: "   0: <std::backtrace::Backtrace>::create\n   1: conjure_error::error::Error::new\n   2: conjure_error::error::Error::service_inner\n   3: conjure_error::error::Error::service\n   4: cli::cli::import::ontology::execute::{{closure}}\n   5: cli::cli::execute::execute_command::{{closure}}\n   6: foundry::main::{{closure}}\n   7: tokio::runtime::park::CachedParkThread::block_on\n   8: tokio::runtime::context::runtime::enter_runtime\n   9: tokio::runtime::runtime::Runtime::block_on\n  10: foundry::main\n  11: std::sys::backtrace::__rust_begin_short_backtrace\n  12: std::rt::lang_start::{{closure}}\n  13: std::rt::lang_start_internal\n  14: _main\n",
    },
)

If I understand it correctly it’s telling me it received a `decimal` type which is unsupported. The problem is I don’t know the object or property that is using type decimal, or if it is something else. Is there a way to dig deeper into this error so I can get unstuck?

2

Hey,
Looks like the problem is an imported action type contains a decimal parameter which is unsupported at the moment. As a follow up we will add support for this, and try to increase visibility for the actual entities that are invalid during import