Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Copy runs from a local repo to a remote repo #2481

@hadim

Description

@hadim

I am trying to copy runs from a local repo to a remote one. I am using aim 3.15.2.

Here is the script to reproduce:

import aim

# Source repo
source_repo = aim.Repo("/a/local/aim/path/")

# Destination repo
destination_repo = aim.Repo("aim://11.22.55.88:53800")

# Get the hashes of the runs to transfer
# Here we take all the runs
run_hashes = source_repo.list_all_runs()

# The copy tasks are batched
batch_size = 20

for i in range(0, len(run_hashes), batch_size):
    batch_run_hashes = run_hashes[i : i + batch_size]
    success, remaining_runs = source_repo.copy_runs(batch_run_hashes, destination_repo)
    
    assert len(remaining_runs) == 0

The error is:

Error while trying to copy run '69c5c7754f3941aaa749af5e'. __enter__.
Error while trying to copy run '61aaf5c37bb4463d8b64b694'. __enter__.
Error while trying to copy run '44fcaaa2717e4c2a9c1008b9'. __enter__.
Error while trying to copy run '0435aa6bee654140aec276aa'. __enter__.
Error while trying to copy run '438b0316ab9341fea0c6ba0b'. __enter__.
Error while trying to copy run '1476377bd2fa4a3591583850'. __enter__.
Error while trying to copy run 'e6c68ffa92f94e2f9b48774a'. __enter__.

After looking at the code in aim/sdk/repo.py, it turns out for remote repo, the attribute structured_db is set to None.

My questions are:

  • Is it indeed the case that the copying runs to a remote repo is not supported? If that's the case, then I would recommend displaying a clear error message.
  • Are you planning to support it?
  • Can you think of a workaround waiting for a potential fix?

Metadata

Metadata

Assignees

Labels

area / SDK-storageIssue area: SDK and storage related issueshelp wantedExtra attention is neededtype / bugIssue type: something isn't working

Type

No type

Projects

Status

Patch-issues

Relationships

None yet

Development

No branches or pull requests

Issue actions