Brian Cipriano

Looks like the test failures here are due to #1192 and are not related to this change.

I hit this the other day too. I was working on various other things at the time so I thought it was related to that, but it looks like something's...

I gave this a try in my local environment. It's not exactly a vanilla setup -- it's `master` plus a bunch of other fixes I have in progress at the...

Just noticed -- I see in that log you posted: ``` killMessage OpenCue could not verify this frame ``` That message means that Cuebot killed the frame because it thought...

BTW I'm working to get a new release out ASAP. A few issues have unfortunately slowed this down -- #1192 in particular has been breaking our CI pipelines that we...

I tried another `sleep 1000` job to check out the state of the database. Attaching a Cuebot log here for you to compare against. [cuebot_during_sleep_job.log](https://github.com/AcademySoftwareFoundation/OpenCue/files/9618741/cuebot_during_sleep_job.log) While the job was running...

@DiegoTavares This is ready for review but could use some more testing. As you can see from the last few commits in this branch I found a few spots where...

Awesome, thanks. FWIW PySide6 shouldn't be required to test this, I believe. It could be tested separately. And maybe it should be, to isolate any issues and help unbreak our...

I created https://github.com/AcademySoftwareFoundation/OpenCue/pull/1191 to reduce the log level for now.

Some initial notes on this change: - This PR is currently a mess because I had to merge several other branches in order to test in my local environment. These...