Skip to content
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

Start recording if Galicaster starts up during a scheduled recording window #488

Open
smarquard opened this issue Mar 29, 2017 · 4 comments
Labels
feature Use this label for new features or enhancements

Comments

@smarquard
Copy link

(Thought there was already an issue for this but can't find it, so apologies if it's a duplicate).

Scenario:

  • Scheduled recording from 10am to 11am
  • Galicaster CA is down leading up to 10am (for example no power in venue)
  • Galicaster CA starts up at 10:05am but does not start recording (start time has passed)

Galicaster should start recording if it is during the recording window for a scheduled recording.

Similar to #487 but a different scenario.

@andiempettJISC
Copy link
Collaborator

see checkrepo plugin.
i'm planning a pull request for an update to this to handle annealing broken recordings together
see: https://github.com/UoM-Podcast/Galicaster/blob/r/2.0.x-UoM/galicaster/plugins/checkrepo.py

@Alfro
Copy link
Contributor

Alfro commented Apr 17, 2017

Hi,
Also related to #451

@smarquard
Copy link
Author

Any update on this? This would help improve reliability for edge-cases, e.g. a capture agent that is rebooted shortly before a scheduled recording is due to start, and it misses the start time.

@andiempettJISC
Copy link
Collaborator

@smarquard I'll make a pull request with our current implementation to fix this. Thanks for the reminder

@Alfro Alfro added the feature Use this label for new features or enhancements label Jun 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Use this label for new features or enhancements
Projects
None yet
Development

No branches or pull requests

3 participants