'/%3e%3cpath%20d='M50.3943%2022.237V39.5876H43.5185V22.7481C43.5185%2019.2029%2042.0411%2017.3949%2039.036%2017.3949C35.7325%2017.3949%2034.0778%2019.5338%2034.0778%2023.7585V32.9759H27.2434V23.7585C27.2434%2019.5338%2025.5857%2017.3949%2022.2822%2017.3949C19.2949%2017.3949%2017.8027%2019.2029%2017.8027%2022.7481V39.5876H10.9298V22.237C10.9298%2018.6918%2011.835%2015.8754%2013.6453%2013.7877C15.5128%2011.7049%2017.9623%2010.6355%2021.0028%2010.6355C24.522%2010.6355%2027.1813%2011.9885%2028.9542%2014.6917L30.665%2017.5633L32.3788%2014.6917C34.1517%2011.9885%2036.811%2010.6355%2040.3243%2010.6355C43.3619%2010.6355%2045.8114%2011.7049%2047.6847%2013.7877C49.4931%2015.8734%2050.3963%2018.6899%2050.3943%2022.237Z'%20fill='white'/%3e%3cdefs%3e%3clinearGradient%20id='paint0_linear_89_8'%20x1='30.5'%20y1='0'%20x2='30.5'%20y2='65'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%236364FF'/%3e%3cstop%20offset='1'%20stop-color='%23563ACC'/%3e%3c/linearGradient%3e%3c/defs%3e%3c/svg%3e)
Well folks, sorry about the downtime
The database migration in RC2 was written slightly wrong in such a way that it locked up the database, and since ours is really big, server wasn't able to handle it.
I implemented a fix for the migration and tagged 1.6.0rc3, to be upgraded to instead of rc2. It's sad this wasn't caught during testing 'cause the testing databases aren't big enough. If you already upgraded to rc2 without problems, good for you, you don't have to do anything.
In a classic move I have been in such a haste to get a fix out that I forgot to update the in-code version string, so publicly 1.6.0rc3 is still 1.6.0rc2. But honestly that's probably fine because they are identical, you know
I hope we're done with bugs y'all, I feel like Rick & Morty at the start of last episode
@Gargron Hello, hello!!
South America is here.
@Gargron oo what did I miss?