-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retry ingesting a recording #30
Comments
Should that be a command line option or something on the/a web-ui? On Fri, 22 Jul 2016 01:44:30 -0700
|
A command line option would be a very good start, but being able to |
I did a quick implementation in #33 , but I'm not a good python dev at all, so any suggestions for improvements are very, very welcome. It seems to work just fine for me. |
This has been effectively implemented with the DB integration and process split. |
Not quite (at least not if I did not miss anything). If an upload failed, the status would be set to |
My bad, you are right. |
From discussion: Let's have a re-ingest button in the recording table if state > |
Would be handled by #73, PATCH-ing the event state to |
Todo to get this done:
|
… the recording is in state FAILED_UPLOADING clicking the button will change the status of the recording to FINISHED_UPLOADING by sending a request to the pyCA API. This will modify the state of the recording via PATCH /api/events/<uid> and pyCA will automaitcally try to re-upload the recording. this fixes opencast#30
) Add a re-ingest button This patch adds a re-ingest button in the recording table for recordings in the state `FAILED_UPLOADING`. Clicking the button will change the status of the recording to `FINISHED_UPLOADING`, making pyCA automatically retry ingesting the recording. This fixes #30
If ingesting a recording has failed (e.g. network problems), the user has to ingest the recording by hand outside of pyCA.
It would be nice if pyCA provides a switch (e.g.
pyCA --ingest-now recording-xyz
) that can be used to retrigger ingesting a recording.The text was updated successfully, but these errors were encountered: