Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug on replacing mode git repo url #29

Open
zhiyuli opened this issue Apr 13, 2022 · 0 comments
Open

Bug on replacing mode git repo url #29

zhiyuli opened this issue Apr 13, 2022 · 0 comments
Assignees

Comments

@zhiyuli
Copy link
Contributor

zhiyuli commented Apr 13, 2022

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

  1. 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)
  2. 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.
@alexandermichels alexandermichels added this to the Future milestone Jan 24, 2023
@alexandermichels alexandermichels removed this from the Future milestone Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants