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 am seeing CI retrying a lot of gateway operations, via the ArDrive CLI, due to gateway timeouts. I suspect some of those retries may be asynchronous and so a file either isn't uploaded yet or isn't indexed by the gateway by the time the path manifest is generated using the folder id.
I've seen ArDrive delays on files being "in" folders, which matters because the path manifest is generated using the folder id. So long term, I think we want a more robust check ensuring all files are "in" the folder, prior to generating the manifest; right now, the check only ensure there are >0 files in the folder.
We could probably add an explicit count here, based on count of local artifacts uploaded or maybe using jq to parse the previous command stdout and count the files created. Either way, this line is where we would check the count is what we expect.
Current workaround is to simply run the CI again, as the issue with missing files seems intermittent, more reason to suspect that gateway indexing delays, or bundler delays, may be the root cause.
The text was updated successfully, but these errors were encountered:
I am seeing CI retrying a lot of gateway operations, via the ArDrive CLI, due to gateway timeouts. I suspect some of those retries may be asynchronous and so a file either isn't uploaded yet or isn't indexed by the gateway by the time the path manifest is generated using the folder id.
I've seen ArDrive delays on files being "in" folders, which matters because the path manifest is generated using the folder id. So long term, I think we want a more robust check ensuring all files are "in" the folder, prior to generating the manifest; right now, the check only ensure there are
>0
files in the folder.We could probably add an explicit count here, based on count of local artifacts uploaded or maybe using
jq
to parse the previous commandstdout
and count the files created. Either way, this line is where we would check the count is what we expect.Current workaround is to simply run the CI again, as the issue with missing files seems intermittent, more reason to suspect that gateway indexing delays, or bundler delays, may be the root cause.
The text was updated successfully, but these errors were encountered: