Jump to content

Mazidox Linden

Lindens
  • Content Count

    81
  • Joined

Community Reputation

290 Excellent

7 Followers

About Mazidox Linden

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yeah, the issue only affects RC channels; it's a knock on effect from some internal fixes we deployed to RC today.
  2. Hi there everyone! As you may have noticed in my previous announcement, some of the regions we recently brought back online on Aditi are in the cloud! We've now expanded the number of regions we're running in the cloud on Aditi to include the entirety of the Blake Sea mainland regions. For those of you who aren't familiar with Blake Sea, you can use the following entry points to log in on Aditi and rez a vehicle to start exploring. If you're not familiar with Aditi itself, you can learn more here. Entry points: Blake Sea - Japan (secondlife://Aditi/secondlife/Blake%20Sea%20-%20Japan/207/248/22) Blake Sea - Beagle (secondlife://Aditi/secondlife/Blake%20Sea%20-%20Beagle/207/208/13) Blake Sea - Mainbrace (secondlife://Aditi/secondlife/Blake%20Sea%20-%20Mainbrace/211/241/16) Blake Sea - Atlantic (secondlife://Aditi/secondlife/Blake%20Sea%20-%20Atlantic/245/219/16) Objectives: Test region crossing code (particularly using vehicles) between cloud simulators on the same host, and cloud simulators on different hosts. Known Issues: Some regions cause you to "bounce off an invisible wall" at the region border, even though you are able to see into them. Please report instances of this occurring in this thread, with the region you were in, the region you were trying to enter, the date, and the time. Some regions will not show up at the edge of your current region, even though they are adjacent. Please report instances of this occurring in this thread, with the region you were in, the region that failed to appear, the date, and the time. HTTP-out for LSL scripts is disabled on cloud-based regions. Please don't report this, as it is currently working as intended. Sending email via LSL scripts is disabled on cloud-based regions. Please don't report this, as it is currently working as intended.
  3. Topic. Sorry they were down for so long, the host they were running on got confused as to what "running" meant, and as you may infer from our blog post in May we don't have a ton of extra hardware to give the beta grid.
  4. That is exactly why these values are read-only for now. We need to get together new viewer code to make it clear to everyone exactly who and what will be able to hear you when you use various forms of local chat.
  5. Second Life Server (No Roll): https://releasenotes.secondlife.com/simulator/2020-06-01T21%3A26%3A43.543116.html Second Life RC: https://releasenotes.secondlife.com/simulator/2020-06-05T19%3A36%3A41.543337.html Wednesday 2020-06-10 07:00-11:30 PDT On Region Restarts: Regions will be restarted if they have been running for more than 10 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 interruptions.
  6. Things are in flux right now, we're building a new version of the release currently on all RC hosts. Our current plan is to put an updated RC with the correct certificates to fix BUG-228850 tomorrow, June 2nd at 3 AM Pacific Time. Then on Wednesday, June 3rd we will put that build on all hosts on the main grid (assuming we don't have any problems with it overnight, we'll be watching for reports of such!). Formal release notes forthcoming, but I wanted to give everyone who frequents this forum for our deploy plans as much notice as possible that it will be a slightly strange week. We'll also be communicating this through other channels.
  7. The answer to that question is "both" and "it depends". Sometimes it's a problem with using an older base version of code to start a project and trampling over fixes that were made in the mean time, other times it's more like the domino effect you describe. I've certainly seen both types of regressions, though I'd be hard pressed to say which is more common. (None of this is EEP specific, I'm just speaking from experience testing various kinds of server changes.)
  8. Per Grumpity's response on https://jira.secondlife.com/browse/BUG-228848 we're aware of the issue and investigating. Please keep up to date with this issue at https://status.secondlifegrid.net/incidents/r64gmw3383q3
  9. Capabilities are the way the Second Life viewer maps a URL that's just for you and your current session to the internal resources on our servers needed to make your connection to the simulator fully functional. It provides things like the ability to download offline IMs reliably, fetch chunks of your inventory, or send an Abuse Report when someone has broken the Terms of Service or Community Standards. The most important capability though is the "Seed Capability" which is the capability to get capabilities. Without that, almost nothing works, as mentioned above. We know some of the ways a server can look when it's not properly handing out capabilities, but I won't say we know what every case of capability failure looks like. We don't have a magic solution to make Capability failures go away (and if we did we'd be releasing it as soon as we could!), but we know it has a big impact on Residents' ability to enjoy their time in Second Life and it's never very far from our minds when we're thinking about ways to improve Resident experience.
  10. That will be 539684 and it should be everywhere on the grid by the end of Wednesday's roll.
  11. Second Life Server: https://releasenotes.secondlife.com/simulator/2020-04-03T19%3A49%3A49.539684.html Scheduled Tuesday 2020-04-14 03:00-09:00 PDT Second Life RCs: https://releasenotes.secondlife.com/simulator/2020-04-10T18%3A15%3A50.540032.html https://releasenotes.secondlife.com/simulator/2020-04-10T18%3A39%3A41.540037.html Probably not an updated release of https://releasenotes.secondlife.com/simulator/2020-03-30T23%3A37%3A53.539435.html as we need to fix BUG-228456 Scheduled Wednesday 2020-04-15 07:00-10:30 PDT On Region Restarts: Regions will be restarted if they have been running for more than 10 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 interruptions.
  12. Yes you can! It will be up shortly. I was hoping for a build to finish before posting, but it looks like that's not going to happen tonight. Edit: Some of it will. Computers are not being my friends tonight, so I'm going to put the RC notes up in the morning. Sorry about that!
  13. Just to chime in here that we're aware of this issue (as mentioned up-thread it's not particularly new unfortunately, dating back to late last year), and using the latest information you all have provided we're able to confirm that the issue under discussion (object_rez events never fire) reproduces in the regions mentioned, but work fine in other regions running the same code. We're not sure why that is just yet, but we're going to do our darnedest to find out and get a fix for this behavior in your hands as quick as we can.
  14. We've managed to find bugs that are either showstoppers or require a rebuild in all 3 of the RCs we had prepped for this week (shoutouts to my awesome colleagues for working on so many simulators this week!), so please expect a roll-less Wednesday, with restarts sprinkled in for regions that have been running over 10 days. As far as release notes, last I heard a meeroo ate the signing key for the release note generator and they're hoping to make another one soon. Nonetheless, the headlining feature for 536748 is that we fixed several memory leaks, particularly in region crossing and LSL script initialization. If you notice any new and unfortunate behavior in those areas, please file a bug at jira.secondlife.com
  15. Hello everyone, We have a large load of release candidate simulators this week, and we're still testing some of them today. I can share that we are planning on promoting 2020-02-14T20:17:32.536748 to Second Life Server tomorrow, and we'll have further updates on which simulator or simulators make the RC cut either this evening or tomorrow (Pacific Time).
×
×
  • Create New...