Upload to B2 churning through Class C Transactions

[jimgoldstein]

Hi My 250GB upload to B2 via Cyberduck cut short when my Daily Class C Transactions hit their 2500 free cap. I've since increased this to 1,000,000+, but in my attempt to resume my upload the following happened.

1. It appears more API calls are being made and counted against my 1,000,000 for assessing files that have been uploaded and remain to upload. I'm not 100% sure if that is happening but I think it is.

2. During #1 the program crashed. It reported back the event automatically it appears.

3. I got an error on a large file that is 1.3GB in size during the file prep. Not sure why.

4. I noticed that the log drawer doesn't show past events until the log drawer is opened. This forced me to repeat my actions to see what the event was in the log.

5. When I resumed my upload registers as 0B

The good news is that things resumed but it took two tries. Let me know what is going on with the Class C transactions for resumed uploads please.

Thanks

Jim

[dkocher]

It is a known issue that we use too many Class C transactions because we use a single upload URI (b2_get_upload_url) for each file.

[dkocher]

Please attach the file cyberduck.log and the crash reports saved in a folder named CrashReporter in the ​application support directory.

[dkocher]

In r20181.