As always, please refer to the server deployment thread for the latest updates and news.
On Tuesday, May 9th, the Main (SLS) server channel was updated with the server maintenance package previously deployed to the LeTigre RC channel, containing sim logging improvements.
On Wednesday, May 10th, the RC channels should be updated as follows:
- BlueSteel and Magnum should receive a server maintenance package with “internal updates”
- LeTigre should receive a server update comprising a new version of the simulator code built using a newer version of Linux. This has previously been on test both on Aditi and the Cake micro-channel. In the words of the Lab, it sees pretty much everything change.
Commenting on the current underpinning server updates the Lab are carrying out, Simon Lab said, at the Simulator User Group meeting on Tuesday, May 9th:
We have some internal projects that are pretty big that will occupy us for months at this point. They’re needed and will help set up SL for a long-term life … it really is investing in the future … Imagine what our back-end systems look like. The design is ancient, it’s been added-on and adjusted for 14+ years. Sometimes we have to stop and do overhauls.
A Maintenance RC viewer is anticipated this week. However, at the time of writing there have been no updates since the end of week #19, leaving the viewer pipelines as follows:
- Current Release version: 184.108.40.2065124, dated April 3rd, April 19th – formerly the Maintenance RC viewer overview
- Release channel cohorts:
- Project viewers:
- Obsolete platform viewer version 220.127.116.110847, dated May 8th, 2015 – provided for users on Windows XP and OS X versions below 10.7.
Group Chat Issues
Group chat on some of the larger groups again seems to be acting up – messages being dropped, people unable to send messages, etc.
Should you encounter repeated / severe issues with group chat, the recommendation is to file a support ticket with a request in the format of: “group XX is suffering excessive chat lag, please check its server”, where XX is the name of the group itself. All such requests should be passed on to Operations, who will take a look at the server responsible for managing that particular group’s chat sessions.