Closed
Bug 1063172
Opened 10 years ago
Closed 10 years ago
Able to submit the same app multiple times to the low-memory review queue
Categories
(Marketplace Graveyard :: Developer Pages, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
2014-09-09
People
(Reporter: krupa.mozbugs, Assigned: mstriemer)
References
()
Details
Attachments
(1 file)
1.06 MB,
image/png
|
Details |
steps to reproduce: 1. Submit an app 2. Before setting up the Content Ratings, submit the app for low-memory support a dozen times since clicking the button creates a 201 but keeps the button enabled. 3. Set up content ratings 4. Approve the app from the regular review queue 5. Load https://marketplace-dev.allizom.org/reviewers/apps/queue/additional/tarako expected behavior: Irrespective of when the app is submitted to the low-memory review queue, it should only get submitted once. actual behavior: App can be submitted multiple times Same app gets listed multiple times in the review queue
Reporter | ||
Updated•10 years ago
|
Summary: 500 on loading /status page of apps → Able to submit the same app multiple times to the low-memory review queue
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → mstriemer
Assignee | ||
Comment 1•10 years ago
|
||
Good catch. This one was a little weird. Two bugs: the check to limit pending reviews was only checking apps that were approved/public, and the link to the status page put an anchor in the URL so `window.location = window.location` would take you back to the anchor instead of refreshing the page. https://github.com/mozilla/zamboni/pull/2509
Status: NEW → ASSIGNED
Assignee | ||
Updated•10 years ago
|
Target Milestone: --- → 2014-09-09
Assignee | ||
Comment 2•10 years ago
|
||
https://github.com/mozilla/zamboni/commit/4c629414489d7180ef2c94d52236ccd913351790
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 3•10 years ago
|
||
Verified as fixed . We are not able to request many tarako reviews because the button is not available anymore after first request.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•