Closed
Bug 1154490
Opened 9 years ago
Closed 9 years ago
Need additional event status (eg. "processing")
Categories
(Webtools Graveyard :: Air Mozilla, defect, P1)
Webtools Graveyard
Air Mozilla
Tracking
(firefox40 affected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox40 | --- | affected |
People
(Reporter: richard, Unassigned)
Details
Need a status named processing that leaves the event visible and in the iCal feed, even though Vidly hasn't finished processing.
Reporter | ||
Updated•9 years ago
|
Priority: P2 → P1
Comment 1•9 years ago
|
||
We need to incorporate this status in all queries to be `status = 'scheduled' or status = 'processing'`
Summary: Need additional event status. → Need additional event status (eg. "processing")
Comment 2•9 years ago
|
||
Gloria, This might be a bit more challenging bug for you. Basically, list of available statuses events can have are these: https://github.com/mozilla/airmozilla/blob/0a2e3a4b6aac8792f843c656d81ac55a90268bf1/airmozilla/main/models.py#L259-L263 We need to introduce another one called Processing (processing). At the moment, what we do is this: 1) The upcoming (future) event is entered and planned. It gets scheduled. It appears in people's calendars, RSS readers, etc. 2) The event goes live, a recording is made and when the event is over the recorded file is uploaded to S3 for transcoding by Vid.ly. Whilst waiting for Vid.ly to transcode it the event goes from "Scheduled" to "Pending" (because it's pending a successful Vid.ly transcoding). 3) When Vid.ly tells us the transcoding is finished, we flip the event from "Pending" back to "Scheduled" and the event is ready and archived. The problem this; You look at the calendar and see an upcoming event. But suddenly it disappears! You think you've got the wrong information or something and the event can't be found. It would be better to be able to see the event at least. And a link to it. On that page we'll say "Hey, thanks for stopping by. We're currently transcoding this. Please be patient and check back in a couple of minutes". So, wherever we rely on displaying events (browsing, searching, iCal, RSS, sidebar) we almost always rely on this piece of code: https://github.com/mozilla/airmozilla/blob/0a2e3a4b6aac8792f843c656d81ac55a90268bf1/airmozilla/main/models.py#L213-L214 A) We need to change that to be status=Scheduled OR status=Processing B) When someone goes from Live to Vid.ly transcoding (I can show you this later) instead of setting status=Pending we need to use status=Processing
Comment 3•9 years ago
|
||
You might wonder, why not change the query to `status=Scheduled OR status=Pending` instead? The reason is that file uploads that were never Live (or Upcoming) you should not see until the transcoding is fully finished.
Comment 4•9 years ago
|
||
I have submitted a pull request for this bug here: https://github.com/mozilla/airmozilla/pull/310
Comment 5•9 years ago
|
||
Commits pushed to master at https://github.com/mozilla/airmozilla https://github.com/mozilla/airmozilla/commit/b29a2226b832e488eab7a4ccc8c85998efe1979a fixes bug 1154490 - Need additional event status (eg. processing) https://github.com/mozilla/airmozilla/commit/d9f559f7b75aca79818dcad8c281f956e22f6d24 Merge pull request #310 from blossomica/bug1154490-Need-additional-event-status-eg-processing fixes bug 1154490 - Need additional event status (eg. processing)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•