Jump to content

Deploy Plans for the week of 2018-05-07


You are about to reply to a thread that has been inactive for 1096 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Second Life Server:

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/18#18.04.30.515008

Scheduled Tuesday 2018-05-08 03:00-09:00 PDT

Second Life RC BlueSteel:

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/18#18.05.07.515224

Scheduled Wednesday 2018-05-09 07:00-10:30 PDT

Second Life RC LeTigre:

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/18#18.05.07.515224

Scheduled Wednesday 2018-05-09 07:00-10:30 PDT

Second Life RC Magnum:

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/18#18.05.07.515224

Scheduled Wednesday 2018-05-09 07:00-10:30 PDT

On Region Restarts:

Regions will be restarted if they have been running for more than 14 days on Tuesday (Main Channel) and Wednesday (RCs) regardless of whether or not new code is being deployed, for the general health and well being of the Simulators.  Nothing beats turning it off and then on again … once in a while.

As always, please plan events around these maintenance windows.  However, if you are hosting an event on Tuesday or Wednesday when we’re not deploying new code, you can restart your region ahead of time to avoid interruption.

  • Like 2
  • Thanks 3
Link to post
Share on other sites

 

Quote

 

18.05.07.515224

  • Scheduled for 2018-05-09 for RC BlueSteel, RC LeTigre, RC Magnum

Changes

 

Awesome!

is Snack in sync with 515224, or will it remain on the previous build, or will it go now that 515008 will hit main with those changes in them?

Edited by Callum Meriman
Link to post
Share on other sites
On 5/7/2018 at 7:46 PM, Callum Meriman said:

 

Awesome!

is Snack in sync with 515224, or will it remain on the previous build, or will it go now that 515008 will hit main with those changes in them?

RC Snack is on hiatus for now until we have need of another small RC cohort, all regions that were on RC Snack have been moved to the Second Life Server channel.

On 5/8/2018 at 9:40 AM, Sayrah Parx said:

Some main channel regions got restarted a second time.  The ones I know for sure are Twice Right and Gama, about 60 minutes and 90 minutes after their first restarts respectively.

I can't really speculate as to what might cause that to happen, that'd be more of an operations question, sorry! If you own either of the regions in question I would recommend reaching out to our wonderful support team at https://support.secondlife.com

17 hours ago, animats said:

18.04.30.515008 did not fix the half-unsit bug. Ref: https://jira.secondlife.com/browse/BUG-214653#comment-559639

Short video. The test is simple - add 1 second of network lag with a test program, aim vehicle at a double region crossing. Instant fail.

We didn't aim to fix the "half-unsit" bug with the changes currently on the Second Life Server and RC channels. It's on our radar though.

  • Like 3
  • Thanks 4
Link to post
Share on other sites

 

That doesn't appear to work. It does return a key, but never the correct one. Here are 3 goes at it, all for the same account, but with capitalisation slightly different:-

b3022afa-461e-e689-1f11-b386f3019a2b Phil Deakins
9731ea3f-6197-b471-438a-b3eca9e4f7a4 phil deakins
9521353b-aade-415e-9c82-b763e054340b Phil deakins

None of the keys are correct - not even the first one which has the correct captalisation.

The correct key is ed2d0c19-77e4-4553-b35c-a120bb64b90f.

When I try the same name, correctly captalised, llRequestUserKey() returns a different key every time:-

default
{
    touch_start(integer total_number)
    {
        integer i;
        string name = "Phil Deakins";
        
        for(i=0; i<10; ++i){
            llOwnerSay((string)llRequestUserKey(name));
        }
    }
}

It returns 10 different keys, none of which is the correct one. As it is now, it's not going to be any good when name changing comes in. I'm not familiar with reporting bugs these days. How is it done?

ETA: I've managed to report this bug - https://jira.secondlife.com/browse/BUG-216256

 

Edited by Phil Deakins
  • Thanks 1
Link to post
Share on other sites
On 08/05/2018 at 3:46 AM, Callum Meriman said:

New LSL Functions:

As well as llRequestUserKey() not working, llName2Key() is restricted. It will only return the key of an agent that's in the sim. It can't be used in the same way that llKey2Name() is used. It's not a bug. It's designed that way, although I can't imagine why. I think that, for most uses, it's adequate, but not for all uses. Imo, it falls short.

Link to post
Share on other sites
2 hours ago, Phil Deakins said:

    •             llOwnerSay((string)llRequestUserKey(name));

Phil, you are using it wrong.

It;s a data server, the return is a just a query handle, you need a data server section to actually get the key.

 

12 minutes ago, Phil Deakins said:

It's designed that way, although I can't imagine why.

Yes, inside the sim means it doesnt need the overhead and logic of a dataserver call. It's faster and has it's place.

Edited by Callum Meriman
  • Thanks 2
Link to post
Share on other sites

Really? Wow! There's no info about it in the LSL wiki yet, and the tooltip text gives no indication of that, so I'd no idea. Maybe it's mentioned in the release notes, which I didn't read.

I'll try it that way, and close the jira if it works :)

Ty, Callum.

Link to post
Share on other sites
2 minutes ago, Phil Deakins said:

Really? Wow! There's no info about it in the LSL wiki yet

 

Quoting the wiki, first line:  "Requests the Agent ID for the agent identified by name from the dataserver."

Example on the wiki:

key name_key_query;
default
{
   state_entry()
   {
       name_key_query = llRequestUserKey("rider.linden");
   }
 
   dataserver(key queryid, string data) 
   {
       if ( name_key_query == queryid )
       {
           llSay(0, "The key for this user is : " + data);
       }
   }
}

 

Edited by Callum Meriman
  • Like 1
  • Thanks 1
Link to post
Share on other sites

 

18 hours ago, Mazidox Linden said:
On 08/05/2018 at 12:40 PM, Sayrah Parx said:

Some main channel regions got restarted a second time.  The ones I know for sure are Twice Right and Gama, about 60 minutes and 90 minutes after their first restarts respectively.

I can't really speculate as to what might cause that to happen, that'd be more of an operations question, sorry! If you own either of the regions in question I would recommend reaching out to our wonderful support team at https://support.secondlife.com

I still see this periodically as well. Could be BUG-134297 Issue with region restarting then restarting again with version change.

 

  • Thanks 1
Link to post
Share on other sites
You are about to reply to a thread that has been inactive for 1096 days.

Please take a moment to consider if this thread is worth bumping.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...