Server

The news and server cycles are off this week because of the US holiday on Monday. We are getting information in small bits. Today via Grid Status we are advised that the Magnum release channel is getting a roll out and will be restarted.

It looks like Magnum is getting the code from Blue Steel plus the fix for SVC-8208 – L$ received notification not appearing when on an RC region. Some Lindens were absent from the typical user group meetings they attend. I surmise they were working on a fix for SVC-8208. Oskar Linden was not sure yesterday the fix would be ready for a Wednesday roll out. It seems they made it.

Read more

The Tuesday rollout to the main channels is going to happen, provided nothing goes wrong over the weekend. As of late Friday it looked as if the Magnum channel would roll to the main channel. That update contains these fixes:

• SVC-7641: Object on land sending excessive messages. The messages sent from the simulator about objects now contain location information, making them easier to find and return.
• SVC-8146: llRezAtRoot() does not set correct parameters (for sale) on rezzed object in Second Life RC BlueSteel 12.08.03.263047
• SVC-7641: Add object location info to messages, was “Object on land sending excessive messages”
• SVC-8124: Excessive “ParcelOverlay reliable” messages sent by regions since last rolling restart (2012-08-08)
• SVC-8136: Attachment point pelvis not being released

Magnum does contain the SVC-8124 fix that most acknowledge as the one that will fix the high bandwidth use problem.

Simon Linden says the code on Magnum has the same fixes as are on Blue Steel, but with more fixes. I think he means more fixes as in more work was done on the items listed rather than more items were added. But, more item fixes are listed as running on Blue Steel than Magnum. So, one is left wondering if Simon is a bit behind, skipping detail, I’m missing his point, or I figured it out.

Read more

Baker Linden gave us an update on the large group editing fixes that are in progress saying, “I just finished up most of the group management stuff. The viewer is loading data successfully, and it should display everything as it did before. I’ll probably hold off on pushing it to QA until Tuesday, as I really don’t like dong commits late in the day, the day before the weekend. But I’m going to get everything ready to go out first thing Tuesday.

I’ll be working with Oz Linden to help me figure out how to deliver a developer preview build of the viewer for people to see the new code, and I’ll be working on documenting the new way group data is managed.

Le Tigre

It has gotten a little confusing as to what is or is not running in the Le Tigre release channel. It is officially now reported as an infrastructure package with no anticipated changes for the regions. There is some rumor that these are network exploit fixes. But, it is hard to know. Others have said it is an isolated SVC-8124 fix for the bandwidth problem, which is what I’ve been thinking. I’m at the point I just don’t know. I lean toward the network exploit fixes now. But, since we can’t see any operational differences the point is mostly moot.

SVC-8177

SVC-8177 – here is different behavior between the RC channels and the main channel involving permissions, objects loose modify permissions. This problem may be the sole reason that nothing rolled to the main channel this week. The RC’s are running a fix for the problem. However, there are some reports the problem persists.

Read more