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
There is a bug or edge case that would happen when replacing the git repo URL in DB for an existing registered model.
Compute Server git clones model repo from the URL that is recorded in DB. If the URL is changed, Computer will not git clone from the new repo URL. Instead, it continues to use the previously git-cloned old repo because the repo folder with the same name already exists.
This affects
rest endpoint /git which would list mixed old and new info: model repo URL is new (from updated DB), but job manifest info is old (read from git-cloned old repo)
the "executable" folder on HPC: the contents are copied/SCP'd from Compute server, so in this case it continues to use the old repo.
The text was updated successfully, but these errors were encountered:
There is a bug or edge case that would happen when replacing the git repo URL in DB for an existing registered model.
Compute Server git clones model repo from the URL that is recorded in DB. If the URL is changed, Computer will not git clone from the new repo URL. Instead, it continues to use the previously git-cloned old repo because the repo folder with the same name already exists.
This affects
The text was updated successfully, but these errors were encountered: