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
I am doing the following: $ gto show <artifact_name>#develop -r <remote_repo_url> --version
And I get the following output:
❌ Unexpected error: list index out of range
Please report it here running with '--traceback' flag: <https://github.com/iterative/gto/issues>
I believe the command should output empty string in this case, as develop stage does not exist yet.
gto show <artifact_name>#develop -r <remote_repo_url> --json gives [], so I guess it could be checked for emptiness?
$ gto doctor:
🪴 GTO Version: 0.2.7
---------------------------------
INDEX='artifacts.yaml'
TYPES=None
STAGES=None
LOG_LEVEL='INFO'
DEBUG=False
ENRICHMENTS=[]
AUTOLOAD_ENRICHMENTS=True
CONFIG_FILE_NAME='.gto'
EMOJIS=True
---------------------------------
✅ No issues found
PS:
Passing --traceback says No such option: --traceback for some reason
The text was updated successfully, but these errors were encountered:
For --traceback option, it should be put in the beginning: gto --tb show <artifact_name>#develop -r <remote_repo_url>
Do you mind contributing a fix? This should be adding a few lines, just like you described. The CI/CD will check your PR for issues - if something won't work, I'll help figuring it out.
Hello! I am getting this error when I try to get the last version of the artifact at the non existent stage.
Let's say I have the following registry:
$
gto show
:I am doing the following: $
gto show <artifact_name>#develop -r <remote_repo_url> --version
And I get the following output:
I believe the command should output empty string in this case, as
develop
stage does not exist yet.gto show <artifact_name>#develop -r <remote_repo_url> --json
gives[]
, so I guess it could be checked for emptiness?$
gto doctor
:PS:
Passing
--traceback
saysNo such option: --traceback
for some reasonThe text was updated successfully, but these errors were encountered: