How are "App Releases" quotas calculated?

oshawkat

We saw our first "Quota almost reached. 1.2 GB of storage left." warning on the Luxonis Hub

yesterday so I removed all the outdated versions of our single app and the message disappeared by the next morning. However it still showed ~12GB used for 2-3 versions of a ~1.2 GB app (according to the .oakapp files).

I saw the warning again today so I removed the app completely from the Hub assuming it would drop to ~0 but it's showing ~18GB used

OskarSonc

Hey oshawkat - could you send us your team identifier so our team can take a look into this?

Best,
Oskar

oshawkat

OskarSonc Yes our team identifier is "onesix"

OskarSonc

oshawkat our team is looking into this, thanks for the wait...

oshawkat

OskarSonc Thanks for looking into this! Any updates? We're still seeing the warning and bumping up against the limit

OskarSonc

oshawkat - the fix in it, so should work from now on!

Thanks for the wait.

Best,
Oskar

oshawkat

OskarSonc Thanks - I now see that we have much more free space on our account!

Can you explain how the "App Releases" quota is calculated? What was going wrong in this instance? That would help us and others viewing this ticket to understand how to avoid this issue in the future

oshawkat

For example, I was just trying to publish another version of our app. The publishing of our 1.2GB app failed with the error below but our App Releases quota still increased from 3.6GB to 4.8GB

Downloading app com-abc-oak-pipeline_1-1-7.oakapp...
✔ Download complete                                                                                        App downloaded into /home/strong/Documents/oshawkat/abc-track-optics/oak/com-abc-oak-pipeline_1-1-7.oakapp
Publishing com-abc-oak-pipeline_1-1-7.oakapp
⠹ [00:00:47] [██████████████████████████████████████████████████████████████░░░░░] 1.15 GiB/1.23 GiB (3s)oakctl command failed: 
   0: Hub service at 'https://apps-ingest.cloud.luxonis.com/v1' encountered an error: Unexpected response with status code: 502 Bad Gateway with text: Some(
          "Bad Gateway",
      )
   1: Unexpected response with status code: 502 Bad Gateway with text: Some(
          "Bad Gateway",
      )

App Releases quota usage prior to the above failed publishing:

And showing +1.2GB used in the App Releases quota after the failed publishing:

That failed upload doesn't appear at all in the Luxonis Hub Apps log:

Note that the computer we're building & publishing the app from has a stable, high speed, wired connection

OskarSonc

@oshawkat - thanks for the details. The quota increase after the failed publish is expected temporarily: the upload reserves App Releases quota first, and in some failure(the 502 error in your case) cases it can take a bit of time for that reservation to be cleaned up again. Worst case, that cleanup should happen within about an hour.

What is not expected is the 502 Bad Gateway error itself. We’re investigating that now, since it likely points to the underlying failure and may be why the quota cleanup fell back to the slower path.

Thanks for the wait.

Best,
Oskar

oshawkat

OskarSonc Thanks for looking into it! If it's helpful for your debugging, I got another 502 Bad Gateway error just now when publishing an app:

oakctl app publish com-abc-oak-pipeline_1-2-4.oakapp
Publishing com-abc-oak-pipeline_1-2-4.oakapp
⠇ [00:00:49] [█████████████████████████████████████████████████████████████░░░░░░] 1.14 GiB/1.26 GiB (4s)oakctl command failed: 
   0: Hub service at 'https://apps-ingest.cloud.luxonis.com/v1' encountered an error: Unexpected response with status code: 502 Bad Gateway with text: Some(
          "Bad Gateway",
      )
   1: Unexpected response with status code: 502 Bad Gateway with text: Some(
          "Bad Gateway",
      )

OskarSonc

oshawkat - thanks we identified the issue and should now work, can you try?
Thanks,
Oskar

oshawkat

OskarSonc Thanks I've been publishing this past week with no issues!

OskarSonc

oshawkat - great to hear!
Best,
Oskar