2020 Simulator User Group week #33 summary

PhotoStudio Purple Cows, June 2020 – blog post

The following notes were taken during the Simulator User Group meeting of Tuesday, July 28th, 2020.

Simulator Deployments

Please refer to the server deployment thread for news and updates:

  • On Tuesday, August 11th, the majority of servers were updated to server maintenance update 545966, comprising updates to assist with the cloud uplift work and includes the updated region crossing code that came about as a result of testing carried out on Aditi in relation to running simulators via AWS services (see my previous SUG summary).
  • On Wednesday, August 12th, There should be at least one deployment, which should also include the adjustments made to the region crossing code, so these will be grid-wide.

SL Viewer

  • The Tools Update 2 viewer, version, dated Monday, August 10th, was released and promoted at the de facto release viewer on Monday, August 10th.
  • The Arrack Maintenance RC viewer updated to version on Tuesday, August 11th.

All other official viewer remain unchanged at the start of the week:

  • Release channel cohorts:
  • Project viewers:
    • Custom Key Mappings project viewer, version, June 30.
    • Copy / Paste viewer, version, December 9, 2019.
    • Project Muscadine (Animesh follow-on) project viewer, version, November 22, 2019.
    • Legacy Profiles viewer, version, September 17, 2019. Covers the re-integration of Viewer Profiles.
    • 360 Snapshot project viewer, version, July 16, 2019.

In Brief

  • At least one large in-world group (60K+ members) is reporting group chat issues, vis: people engaged in group chat suddenly not seeing their own text when entered while other receive it; people typing into group chat and seeing their chat appear on entering, but some others saying they didn’t see it and others confirming they can see it, etc. This issue has thus far only bee reported via support ticket and a Jira has been requested.
  • There is a general request that those using the Blake Sea + Morris and Ahern regions on Aditi (all running via AWS) who notice unusual, reproducible issues, to please raise a Jira.

2 thoughts on “2020 Simulator User Group week #33 summary

    1. Because support tickets may be dealt with by the support team for a specific instance of a problem without the underlying cause being recognised as potentially more systemic in nature, perhaps? Because Jira centralises issues and problems in a central tracker that is used across all engineering / operations teams, rather than one primarily contained within the support environment? Because the issue should have been reported by Jira to start with, so that a) it can be properly cross-team triaged both on its own and in conjunction with issues previously reported through this mechanism that may be related / have an impact on the matter, and b) as the Lab would prefer support don’t become a conduit for people to report issues in the hope support will file a Jira on their behalf? A combination of all of these reasons?

      Liked by 1 person

Comments are closed.