Server Deployments – recap
There were no deployments to the Main (SLS) channel or the BlueSteel and LeTigre channels during week 16.
On Wednesday April 16th, the Magnum RC received a new server maintenance package, which included a fix for llTeleportAgent() and llTeleportAgentGlobalCoords() can break any script in any attached object that contains a change event.”).(“
Commenting on the latter at the Server Beta User Group meeting on Thursday April 17th, Maestro Linden said:
Unfortunately, after the roll we discovered that there was a regression in the Magnum update, which was BUG-5763 (“AGENT_MOUSELOOK flag is often incorrect when llGetAgentInfo() is called within control() event”), which apparently affects certain guns (which only allow some actions when they think you’re in Mouselook) and certain vehicles (which change control behaviour when they think you’re in Mouselook).
The good news is that Kelly [Linden] came up with a fix for it yesterday, which is out on Aditi now. I gave it a whirl, and it looks like this bug is fixed. But if you have content that was broken by that bug, I’d encourage you to test it out on Aditi, in case there are any additional problems.
Those wishing to test the fix can do so on the Aditi regions Ahern, GC Test 10, and Tehama. GC Test 10 is probably the most convenient to test on, as it mostly allows anybody to build and run scripts.
Week 17 Deployments
While the final details of deployments for the week commencing Monday 21st April will not be determined until the start of that week, it currently looks as though there will again be no deployments to with the Main (SLS) channel or the BlueSteel and LeTigre RCs, while Magnum will gain the BUG-5763 fix.
Commenting on the lack of high-profile server updates of late, Maestro pointed to the fact that the Lab has been engaged in a series of “invisible updates” recently, notably infrastructure improvements.
Group Chat Update
There were no further tests on Simon Linden’s group chat work, and Maestro indicated that testing on Agni may commence in week 17. An idea initially discussed for testing these optimisations on the main grid had been to use a single large group (the Firestorm Support group, due to both its size and frequency of use). However, commenting on the work, Maestro Linden said, “since the group chat changes are in the backend service, this would mean that … around 1/16 of groups would be on the group chat stuff.”
Some people are noticing an uptick in issues relating to in-world scripts acting as HTTP servers (notably with HTTP-in functions). There has been a known bug with these (non-public BUG-2564) wherein all http-in URLs and all capability URLs for connected users are dropped simultaneously, all the connected users get logged out, and HTTP-in scripts cannot be contacted. However, some of the issues people are experiencing appear to be occurring since the most recent HTTP updates were made. Lucia Nightfire describes the problems as, “random URL loss and instability is common esp after the http changes.” she goes on to note that she has had to “change http protocol and add heartbeats to some apps since the HTTP changes.” She further goes on:
Sometimes after I crash then relog into a region, its like my caps are reset and re-evaled and in-turn all my HTTP devices all of a sudden cannot request URLs until the caps are reset or it is [a] repeat URL request failure. Long story short, if your viewer crashes, don’t log into your home region if you have servers there, or you risk interruption.
Maestro’s thinking on the matter is that it may be linked to a server crash – particularly given Lucia confirms the problem does occur as a result of a region crash – as there is nothing specific to a viewer crash which should upset things like HTTP-in functions. Further testing has been suggested to see if a precise cause can be identified.