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
I understand that files are now collated within an archive. I assume there are reasons for this (perhaps performance or cost oriented?), but it is making the upload/download process more difficult in some cases.
However, when an directory is uploaded (as an archive), only the archive address (XOR) is returned. This makes it hard to know how to directly address the files, unless each are uploaded separately. This assumes that directly addressing the files isn't an issue?
Can the CLI return a list of addresses for each item in the archive, along with the archive address itself? Also, can autonomi file list do the same?
The text was updated successfully, but these errors were encountered:
I agree that this is a problem and have a PR in progress which splits this API into two functions.
One does as now, but is renamed dir_and_archive_upload() and the new function dir_upload() no longer uploads the Archive but returns it so the caller can inspect the content (files uploaded and xor address). This avoids uploading the Archive unnecessarily, which been be done separately if required.
I understand that files are now collated within an archive. I assume there are reasons for this (perhaps performance or cost oriented?), but it is making the upload/download process more difficult in some cases.
However, when an directory is uploaded (as an archive), only the archive address (XOR) is returned. This makes it hard to know how to directly address the files, unless each are uploaded separately. This assumes that directly addressing the files isn't an issue?
Can the CLI return a list of addresses for each item in the archive, along with the archive address itself? Also, can
autonomi file list
do the same?The text was updated successfully, but these errors were encountered: