Closed hagenw closed 4 weeks ago
If a database has several attachments (in this case all attached as folders, haven't checked the case of single files yet), and is loaded with audb.load_to('build/', ...) it might happen that not all attachments are loaded.
audb.load_to('build/', ...)
Assume the following entry in the db.yaml header:
db.yaml
attachments: a-a: {description: 'Attachment a-a', path: a/a/} a-b: {description: 'Attachment a-b', path: a/b/} b-a: {description: 'Attachment b', path: b/a/} c-a: {description: 'Attachment c', path: c/a/}
The expected directory tree of the attachments after loading them would be:
build/ a/ a/ file-a-a-1 file-a-a-2 b/ file-a-b-1 file-a-b-2 b/ a/ file-b-a-1 file-b-a-2 c/ a/ file-c-a-1 file-c-a-2
Instead what we get is
build/ a/ a/ file-a-a-1 file-a-a-2 b/ file-a-b-1 file-a-b-2
So it is only loading two of the four attachments.
I tested with num_workers=8 and num_workers=1, result is the same.
num_workers=8
num_workers=1
I tried to replicate this error in https://github.com/audeering/audb/pull/421, but did not suceed.
If a database has several attachments (in this case all attached as folders, haven't checked the case of single files yet), and is loaded with
audb.load_to('build/', ...)
it might happen that not all attachments are loaded.Assume the following entry in the
db.yaml
header:The expected directory tree of the attachments after loading them would be:
Instead what we get is
So it is only loading two of the four attachments.