administrator/frigate
1
0
Fork 0
mirror of https://github.com/blakeblackshear/frigate.git synced 2026-05-07 14:05:28 +03:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

recording timestamp fix

Browse Source 
when startTime is exactly on an hour boundary, findIndex returns the first matching chunk, which is the previous hour's chunk (where before == startTime), instead of the correct chunk (where after == startTime)

the bug shows up when using the share timestamp feature and sharing a specific timestamp on the exact hour mark. when accessing the shared link, the timeline would jump to the incorrect hour
This commit is contained in:
Josh Hawkins 2026-05-01 10:20:43 -05:00
parent 8aa1e1b373
commit 9c1fb2e5e9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
web/src/views/recording/RecordingView.tsx
View File

@ -170,7 +170,7 @@ export function RecordingView({
);
const [selectedRangeIdx, setSelectedRangeIdx] = useState(
chunkedTimeRange.findIndex((chunk) => {
return chunk.after <= startTime && chunk.before >= startTime;
return chunk.after <= startTime && chunk.before > startTime;
}),
);
const currentTimeRange = useMemo<TimeRange>(
@ -275,7 +275,7 @@ export function RecordingView({
const updateSelectedSegment = useCallback(
(currentTime: number, updateStartTime: boolean) => {
const index = chunkedTimeRange.findIndex(
(seg) => seg.after <= currentTime && seg.before >= currentTime,
(seg) => seg.after <= currentTime && seg.before > currentTime,
);
if (index != -1) {