Closed
Bug 839344
Opened 13 years ago
Closed 13 years ago
Increase Demo Studio / Dev Derby upload limit
Categories
(developer.mozilla.org Graveyard :: Demo Studio / Dev Derby, defect)
developer.mozilla.org Graveyard
Demo Studio / Dev Derby
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: openjck, Unassigned)
References
Details
(Whiteboard: [specification][type:change])
What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
The upload limit used on the Demo Studio and the Dev Derby. The new limit should be at least double the current limit to be sure it is relatively future-proof.
What problems would this solve?
===============================
A few users are hitting the limit, most notably the people behind BananaBread, probably the most important demo on the site.
Who would use this?
===================
Anyone who submits to the Derby, but particularly the authors of BananaBread and (in the future) apps authors.
What would users see?
=====================
N/A.
What would users do? What would happen as a result?
===================================================
Users would be able to upload demos roughly twice as big.
Is there anything else we should know?
======================================
Comment 1•13 years ago
|
||
In order to accommodate this, we really need offline processing of demo .zip files in a queue (bug 632082) so that the submitting user isn't made to wait (and potentially time out) while the upload is processed.
Depends on: 632082
Comment 2•13 years ago
|
||
On the other hand, we can try just bumping the limit up and see if anyone really runs into an issue. Switching to an async/offline demo upload processing model will be somewhat involved.
| Reporter | ||
Comment 3•13 years ago
|
||
Yeah. The goal here is to have a temporary solution. Offline processing and Git submission will solve the underlying problem.
Comment 4•13 years ago
|
||
FWIW, here's where the settings are defined, which require an IT bug to change:
https://github.com/mozilla/kuma/blob/master/apps/demos/models.py#L67
* DEMO_MAX_ZIP_FILESIZE
* Maximum size accepted for a .zip overall
* DEMO_MAX_FILESIZE_IN_ZIP
* Maximum size accepted for any given file contained in the .zip after decompression (though I think this looks for what the .zip lists in its table of contents, and doesn't do a real decompression first)
| Reporter | ||
Comment 5•13 years ago
|
||
Doing the Design phase myself here. This should not have any real impact on design, other than allowing users to submit larger demos.
This might cause a timeout for very large demos (see comment 1) but this is an acceptable tradeoff as we need to increase this limit as soon as possible and the timeout will be seen by very few users if any. The underlying problem will be resolved when we process uploads offline.
Les: I am going to call this done for design, and also mark this "Ready" in the "Technical Research" column based on comment 4.
Comment 6•13 years ago
|
||
Filed IT bug 840149 to add settings to increase the upload limit. This won't result in a pull request to review, and so will skip straight to Released once the IT bug is closed.
| Reporter | ||
Comment 7•13 years ago
|
||
Bug 840149 is closed.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 8•13 years ago
|
||
(In reply to John Karahalis [:openjck] from comment #7)
> Bug 840149 is closed.
Well, yeah, but I haven't had a chance to try this out on prod yet :)
Comment 9•13 years ago
|
||
(that is, wait until I've verified:fixed the IT bug)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•13 years ago
|
||
Ack, sorry about the quick reopen / close. I was in the middle of verifying and it was looking like it was going to timeout and give me an error. But, it looks like the upload went through after about 3 minutes of spinning.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Comment 11•13 years ago
|
||
Going to call this verified too, since I just did so myself.
Status: RESOLVED → VERIFIED
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•