-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: NotEnoughNodeQuotes errors over repeated uploads prevent client uploading #2573
Comments
Thanks for the report. We seen this issue internally, but we resolved it, or at least thought we had. It doesn't occur any more in our own uploads against the live network. Probably good to bring this one to the attention of @maqi . |
I've had variations of this error many times too. It seems worse on this network over the last. I've been struggling to upload a full directory of files. Single files seems more reliable. Iirc, a failure doesn't mean you aren't billed either. It looked like I was paying each retry, the last time I checked. |
We will look into this again. Thanks for the report. |
I've been experiencing the same thing. When a failure occurs (due to not enough node quotes) on a directory upload, sometimes I would still be charged attos. I'm guessing this might be due to some of the files in the directory successfully uploading (but no address given due to the error ending the process). It would be nice to be able to resume a directory upload to avoid redundant file uploads. |
I'm finding the same issue with Autonomi v0.3.1 as v0.3.0 which I reported on the forum, so opening an issue. I've tried the same set of files uploading from both laptop over mobile broadband hotspot and on VPS.
Essentially I have a script which is repeatedly running my client (awe) to upload a directory of about a dozen files until it succeeds, but it always fails to upload one or more files with this error:
The log contains a blend of my client output to terminal and the autonomi log output:
awelog-upload-quicktest.zip
The text was updated successfully, but these errors were encountered: