You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handle cases where artifact is recognized but does not contain Kitfile
Since we're adding support for model-spec artifacts (modelpacks), there
may be cases where we are handling artifacts that do not have a Kitfile
available. As a result, we need to handle the case where a config
(Kitfile) cannot be found:
* Add error type for repo utilities to signify that everything is fine,
except no Kitfile is available
* For inspect, warn that there is no Kitfile and show the manifest
* For list, ignore metadata that we normally retrieve from the Kitfile
(e.g. author and model name)
* For unpack, attempt to generate a dummy config to allow unpacking to
continue:
* Don't unpack Kitfile, as it does not exist
* Use model-spec file path annotations to fill a fake Kitfile with
paths to allow unpacking
Signed-off-by: Angel Misevski <[email protected]>
0 commit comments