This is what we're talking about.
Switch to another browser tab and back again
@tmm1 I'm still seeing the flipping back-and-forth issue on v2024.01.11.0232.
On any airings page with "Recorded" airings, every time the browser viewport focus is regained, the dropdown menu title alternates between 
Recorded ⏷ and ⛭⏷.
Another easy way to reproduce the focus change is to click the URL bar and then click somewhere on the webpage, and then repeat this to see the menu titles alternate each time.
I've recently noticed another symptom of this issue: every time the airings page regains focus, repeated errors are logged to the browser dev console, and at the same time the dropdowns very briefly flash
[ Recorded ⏷] before reverting to [
⏷].
This results in the dropdowns getting "stuck" in the [ ⏷] state.
For example, in the case of a movie airings page with two airings listed, the following is logged to the browser developer console (four times, twice per airing) every time the airings page regains focus:
globals.jsx:162 GET http://192.168.1.5:8089/dvr/jobs/4940 404 (Not Found)
globals.jsx:169 GET /dvr/jobs/4940 Not Found
globals.jsx:162 GET http://192.168.1.5:8089/dvr/jobs/4940 404 (Not Found)
globals.jsx:169 GET /dvr/jobs/4940 Not Found
globals.jsx:162 GET http://192.168.1.5:8089/dvr/jobs/4940 404 (Not Found)
globals.jsx:169 GET /dvr/jobs/4940 Not Found
globals.jsx:162 GET http://192.168.1.5:8089/dvr/jobs/4940 404 (Not Found)
globals.jsx:169 GET /dvr/jobs/4940 Not Found
...where 4940 is the File ID of the existing recording and /dvr/programs/MV001899890000 returns "recorded-4940".
Running latest v2024.01.29.2327 pre-release.
Logs have been submitted as 349e598f-f723-4fc3-9b35-1d9c4d2249bf.
This should fix it. Please let us know if you still see it.
It's not clear from the photos what the series of steps you've done to reproduce this.
Are you seeing 404 requests in the logs like the previous report? Is the gear icon flickering?
Just switching focus away from the web page. Whether to another browser tab or another application and back again.
Nothing interesting in the web console output.
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
Source map error: Error: request failed with status 404
Resource URL: http://192.168.1.4:8190/bundle.css
Source Map URL: bundle.css.map
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
jsonpipe connecting globals.jsx:290:12
jsonpipe connected globals.jsx:295:18
event Object { Type: "hello", Version: "2024.01.30.0358" } globals.jsx:300:16
Using my daily driver, Firefox v122.0 (64-bit)
Can you give me a step-by-step of what you did to get to this issue like the OP?
Been happening for a couple years.
In the DVR web UI select DVR > Passes
select a pass with some recorded and queued items
click the Matches (#) tab
note that items are initially marked correctly as Queued or Recorded
switch focus to another browser tab or application and back again (may have to do this more than once)
Just duplicated in Brave v1.62.153 Chromium: 121.0.6167.85 (Official Build) (64-bit)
And Microsoft Edge Version 121.0.2277.83 (Official build) (64-bit)
1 Like
Might be a hint, but I don't remember the exact Pre-Release version it was introduced in (had to be before you started publishing the release notes here)
I still see the alternating issue on v2024.01.30.0358 unfortunately. The 404 console errors are fixed, but the gear icon still flickers and remains shown when it should not.
I wish I could figure out a simple way to reproduce this on my development environment, but so far I've been unable to produce the results you are all seeing...
Maybe the browser environment? I'm running them on Windows 10 Pro and don't have dev tools open.
I remember a saying, something like
"The act of observing a behavior changes the behavior being observed"
I don't think I've figured out the exact set of completed recordings and queued recordings on a given pass that are required to make it happen. I've tried on Chrome and Safari.
Here's one from the pass Matches tab.
First one is scheduled to record and appears in DVR > Schedule
Later airing of that same episode, opened the dropdown
Switched to another browser tab and back again, dropdown still open, but changed
Thanks everyone. The issue is with multiple airings of the same show where one of them is being queued. I was able to replicate this and track down what was going on. The next pre-release will have the fix.
1 Like
This should be it:
That fixed it 
, but now the previously recorded episodes don't show as recorded in a search or in the pass Matches tab 
.
Can you submit diagnostics and provide the name of an episode you expect to show up but isn't?
