When moving a run to a new project, its logged artifacts stay in the previous project
See original GitHub issueDescribe the bug When moving a run to a new project, its logged artifacts stay in the previous project.
To Reproduce Steps to reproduce the behavior:
- Log an artifact:
import wandb
wandb.init(project='test-project0')
artifact = wandb.Artifact('cities-names', 'cities')
with artifact.new_file('names.txt', 'w') as f:
f.write('Moscow;Amsterdam;New York;')
wandb.log_artifact(artifact)
wandb.finish()
- Then go to the project dashboard and move this run to another project, e.g. “test-project1”.
- Try to use the artifact in Colab (first, copy the run path and replace with variable
run_pathbelow):
past_run = wandb.Api().run(run_path)
logged_artifact = list(past_run.logged_artifacts())[0]
print('artifact project:', logged_artifact.project)
print('artifact name:', logged_artifact.name)
artifact project: test-project1
artifact name: cities-names:v0
then run
wandb.use_artifact(logged_artifact.project + '/' + logged_artifact.name)
Raises exception:
...
<lots of traceback>
...
CommError: Project sobir/test-project1 does not contain artifact: "cities-names:v0"
Expected behavior I should be able to use the artifact
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
When moving a run to a new project, its logged artifacts stay in ...
When moving a run to a new project, its logged artifacts stay in the previous project. ... Steps to reproduce the behavior: Log...
Read more >Job artifacts - GitLab Docs
Keep artifacts from most recent successful jobs · On the top bar, select Main menu > Projects and find your project. · On...
Read more >2.12 Manage Project Artifacts - PM Illustrated PMP Exam
These artifacts are “living documents,” which means they evolve to reflect changes in the project. (They are not static, one-off documents like meeting...
Read more >Publish and download pipeline Artifacts - Azure
Using Azure Pipelines, you can download artifacts from earlier stages in your pipeline or from another pipeline. You can also publish your ......
Read more >Migrating projects - Resource Manager - Google Cloud
If you have mistakenly moved a project, you can roll back the operation by performing the move again, with the old source as...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Bump
It would be nice for the artifacts to move to, or at least to have a way to move them. This has made it difficult for me because now when I want to collect runs and associated artifacts with the API I need to pull from two separate projects.
Hi @cvphelps, thanks the reply. The reason for moving runs was that I wanted to split a project into two. I had two slightly different kinds of runs that were making the dashboard complicated. So, actually the reason was to get separate dashboards for each kinds of runs. I think it’s not an issue for me now, since I learned to use reports instead for that purpose.
PS: by “dashboard” I meant workspace, where charts are organized.