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

Don't allow unlimited unprocessed segments to stay in cache #14341

Merged
merged 2 commits into from
Oct 14, 2024

Conversation

NickM-27
Copy link
Sponsor Collaborator

Proposed change

This ensures that if a detection process fails for a longer period of time, unprocessed recording segments won't pile up in cache

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • The code has been formatted using Ruff (ruff format frigate)

Copy link

netlify bot commented Oct 14, 2024

Deploy Preview for frigate-docs canceled.

Name Link
🔨 Latest commit a0e4142
🔍 Latest deploy log https://app.netlify.com/sites/frigate-docs/deploys/670d3a15da595900087e2bda

@NickM-27 NickM-27 changed the title Don't allow unlimited unprocessed frames to stay in cache Don't allow unlimited unprocessed segments to stay in cache Oct 14, 2024
@NickM-27 NickM-27 merged commit 3879fde into dev Oct 14, 2024
12 of 13 checks passed
@NickM-27 NickM-27 deleted the improve-recording-handling branch October 14, 2024 22:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants