As always, please refer to the server deployment thread for the latest news.
- There was no deployment of the SLS (Main) channel on Tuesday, April 20th, leaving all regions on that channel on server update 19#19.04.22.526534 comprising performance improvements (possible fixes for teleport / region crossing issues) and additional internal logging.
- On Wednesday, May 1st, all three main RC channels should be updated to server maintenance package 19#19.04.25.526669, primarily intended to correct the simulator-side EEP regressions that resulted of the roll-back of Thursday, April 18th. This update also includes a number of other internal fixes.
There have been no viewer updates at the time of writing this update, leaving the viewer pipelines as follows:
- Current Release version 188.8.131.526190, formerly the Estate Access Management RC viewer, dated April 12, promoted April 17 NEW. – see my EAM overview for more information
- Release channel cohorts:
- Project viewers:
- Linux Spur viewer, version 184.108.40.2069906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 220.127.116.110847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7. This viewer will remain available for as long as reasonable, but will not be updated with new features or bug fixes.
My second Life has been down since the weekend of April 27/28th, 2019. This has affected all access to the site, the upload of snapshots and in-world web-based profiles.
Linden Lab is aware of the issue, and working to resolve the outage.
The teleport disconnect issue is now being seen as a race condition,with Simon Linden commenting:
The TP issue looks like a race condition … we “fixed” 3 other bugs and made that worse.
To which Oz Linden added:
And we’ve already put in place a bunch of improvements to our RC monitors to help prevent a similar recurrence (with more coming soon) … Doubtless Murphy will find new ways to avoid our monitors from time to time, but one tries.
The lab now feel they have investigated the issue and gathered sufficient data around it to be able to perform a post-mortem on the situation to (hopefully) reduce the likelihood of such an occurrence in the future.
Script Processing Issues
This was raised at the April 26th TPVD meeting as well. There have been numerous reports of script run time issues, with some reporting that problems only started occurring following the roll-back on April 18th, 2019. BUG-226851 outlines some of the problems.
As per the TPVD meeting, the Lab are not aware of anything that may have changed to impact script run time (particularly on Full regions); but the problem has been somewhat exacerbated by the issue being bounced between the JIRA and support (note how the above report has been closed, referencing the matter back to support).