Skip to content
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.

[BUG-498] Regions should have a failsafe to deter conditions that prevent capabilites from being granted to agents which prevents region access and prim removal in the region. #13264

Closed
sl-service-account opened this issue Oct 21, 2012 · 4 comments

Comments

@sl-service-account
Copy link

User Story

Recently I have come across a region per week that fails to grant capabilites to agents that attempt to access the region.

Information

These regions prevent region crossing into, teleporting into, logging into the region. Agent online checks from scripted objects in these regions fail. Object instant messages from these regions do not go to their target agents but instead go the target's email if applicable. HTTP url requests fail. People already in a region that drops capabilities cannot chat in group chat even if they already were participating in it. Agent to agent IM's go to the agent's email with a message: "Second Life: User not online - message will be stored and delivered later." even when the recipient is online or already in IM chat with the sender.

Worst of all, prims on parcels in these regions cannot be returned or deleted at all, returning the following system error to prim owners: "Cannot derez object due to inventory fault." The prim owners will get an email that their object(s) were returned despite the fact the objects weren't removed.

Expected Behavior

Regions should have a failsafe to deter conditions that prevent capabilites from being granted to agents which prevents region access and prim removal in the region.

Additional Information

Support does not need to restart a region to fix this issue so there should be something the region can do to deter this condition from even occurring.

Original Jira Fields
Field Value
Issue BUG-498
Summary Regions should have a failsafe to deter conditions that prevent capabilites from being granted to agents which prevents region access and prim removal in the region.
Type Bug
Priority Unset
Status Closed
Resolution Duplicate
Reporter Lucia Nightfire (lucia.nightfire)
Created at 2012-10-21T07:47:38Z
Updated at 2014-03-15T06:51:29Z
{
  'Business Unit': ['Platform'],
  'Date of First Response': '2012-10-25T15:05:26.467-0500',
  'System': 'SL Simulator',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'Recently I have come across a region per week that fails to grant capabilites to agents that attempt to access the region.',
  'What were you doing when it happened?': "These regions prevent region crossing into, teleporting into, logging into the region. Online checks from scripted objects in these regions fail. Object instant messages from these regions do not go to their target agents but instead go the target's email if applicable.",
  'What were you expecting to happen instead?': 'Regions should have a failsafes to deter conditions that prevent to granted capabilites to agents which prevent region access.',
}
@sl-service-account
Copy link
Author

Lucia Nightfire commented at 2012-10-21T15:32:05Z, updated at 2012-10-21T16:38:12Z

Just had this condition occur at approx. 07:50:36 in the region Kenophobe. Someone rezzed the popular replicating inventory offer spam object "[L4L] Gestures & Walkers (Freebies) <3" and several other people accepted and rezzed it as well and after hundreds of these were returned by prim owners list, the region immediately created the condition where capabilities were removed for all agents currently in the region and would not grant them for agents attempting to enter. This means prim removal at that point was impossible for anyone. Teleporting in or out was impossible. Region crossing was impossible. HTTP url requests could not be made.

Another thing to note is that during this issue remote object IMs targeting agents already in this region go directly to their email if applicable.

@sl-service-account
Copy link
Author

Lucia Nightfire commented at 2012-10-23T00:45:12Z

Capabilites failed for the region, Kenophobe again at 17:18:12 today (10/22) as url requesting could not occur from that time until support turned capabilities back on. Of course region access was impossible as well.

@sl-service-account
Copy link
Author

Lucia Nightfire commented at 2012-10-24T21:32:54Z, updated at 2012-10-28T00:30:10Z

Capabilites failed for the region, Kenophobe again at 14:28:15 today (10/24) as url requesting could not occur from that time until support turned capabilities back on. Of course region access was impossible as well and prim removal was impossible for everyone.

Capabilites failed for the region, Kenophobe again at 2012-10-25 @ 18:47:26.
Capabilites failed for the region, Kenophobe again at 2012-10-26 @ 16:01:24.
Capabilites failed for the region, Kenophobe again at 2012-10-27 @ 16:34:51.
Capabilites failed for the region, Kenophobe again at 2012-10-27 @ 17:25:59.

@sl-service-account
Copy link
Author

Maestro Linden commented at 2012-10-25T20:05:26Z

Hi Lucia, thanks for the report. We're well aware of the caps failures issues (there are multiple reasons why capabilities grants can fail), and are working toward solutions for it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant