Patch release v2023.01.17

[bjester]

Summary

This is a patch release to address:

• an issue with having multiple Studio tabs/windows open that may prevent the saving of data on Studio,
• performance improvements to a migration command for upcoming bug fixes and enhancements
• concurrency issues affecting the enqueuing of tasks that results in task duplication

Pull requests

PR	Issues	Category	QA Focus
#3907	#3906	Bug fix	Channel editing (multi-tab)
#3875	#3836	Bug fix	Channel editing
#3913	#3912	Bug fix	Spanish translation 'Reflect' -> 'Reflexionar'
#3892	#3846	Performance	N/A

QA Notes

Multi-tab editing

Goal: Perform various channel editing operations while having more than one Studio tab open
Key aspects to QA:

• open and close tabs during channel editing
• the next day, sign out and back in and verify all edits still exist
• use Firefox on Windows (of course Chrome and Firefox should work on any platform)
• if possible, test on Windows with constrained hardware (1 CPU, 4GB of RAM, see reproduce notes in Opening multiple tabs may prevent proper syncing of channel changes #3906)

[pcenov]

Hi @bjester so far I am not able to replicate the issue described in #3906 and in general syncing of channel changes has been quite stable for me today. Will further keep testing it tomorrow as well.
Incidentally I noticed the following error in Chrome while I was not doing anything at the page, it was just left open:

There are seemingly no user facing consequences. I've also not been able to spot what exactly is causing it so let me know if you think it's problematic.

[pcenov]

I have reported one more issue here: #3914
Also saw the following error in the console at some point, again with seemingly no user facing consequences: Unexpected null ancestor

[bjester]

Thanks @pcenov! We have this enhancement planned for the next major studio release #2850

[bjester]

Hi @bjester so far I am not able to replicate the issue described in #3906 and in general syncing of channel changes has been quite stable for me today. Will further keep testing it tomorrow as well. Incidentally I noticed the following error in Chrome while I was not doing anything at the page, it was just left open:

There are seemingly no user facing consequences. I've also not been able to spot what exactly is causing it so let me know if you think it's problematic.

Also, @pcenov, I believe you've run into this error before. If you didn't notice anything go awry, I don't think it should block the patch release, but it has been something I've looked into and want to resolve.

[radinamatic]

All improvements are looking good, thank you @bjester, !