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

Filtering Timespans returns 0 when starting before any recordings #4164

Open
cooperbrown9 opened this issue Jan 16, 2025 · 1 comment · May be fixed by #4173
Open

Filtering Timespans returns 0 when starting before any recordings #4164

cooperbrown9 opened this issue Jan 16, 2025 · 1 comment · May be fixed by #4173

Comments

@cooperbrown9
Copy link

Which version are you using?

1.11.0

Which operating system are you using?

macOS amd64 Docker

Describe how to replicate the issue

  1. start the server
  2. Record some segments
  3. List recording segments but set the startTime to BEFORE there are any segments http://10.10.10.89:9996/list?path=4f3b9762-967a-4ff2-a085-ec207f3dafb5&start=2025-01-16T15%3A33%3A00.000Z&end=2025-01-16T18%3A33%3A00.000Z

That start time is several hours before i have any recordings for that day. It returns "no recording segments found", even though there are recordings in that timespan, they just are AFTER the start time.

Thank you guys, i love this feature! Just a weird edge case i imagine.

Server logs

I dont think logs would be helpful in this case, nothing to note there

Network dump

nothing to note

@ijessen-mitll
Copy link
Contributor

This affected us too - seems like an easy fix

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 a pull request may close this issue.

2 participants