• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-2359
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: WorkingOnIt Linden
Reporter: Matthew Dowd
Votes: 141
Watchers: 22
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

Capped IMs can cause inventory loss

Created: 17/May/08 04:46 AM   Updated: 11/Dec/09 02:11 AM
Return to search
Component/s: Simulation
Affects Version/s: 1.21.0 Server, 1.24 Server, 1.25 Server
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Relates

Linden Lab Issue ID: DEV-16143


 Description  « Hide
Inventory offers to other avatars are effectively done as a special form of IM.

A result of this is that if your IMs have been capped, any inventory offers to you are silently dropped.

I'm classing this as a bug, as this behaviour may be by design but it is undesirable:

a) in the case of IMs and group notices, you can at least still read these if you enable sending of IMs to e-mail (or view the archived notices in groups) - in the case of inventory offers you can see you received an inventory offer in e-mail but apart from contacting the original sender in the hope they will resend it, you can't get the inventory
b) the sender is not informed that the inventory offer failed, so may believe the person received it - nor is there any way of checking in advance whether the inventory offer would succeed (apart from checking if the person is definitively online, but even online status is not that reliable).
c) if the item offered is no-copy, the item is neither recieved by the recipient, nor returned to the sender if the recipients IMs are capped
d) there are a number of ways in which inventory might be sent whilst offline, and so may fall foul of this - gifts from other avatars, update servers sending out an available update to previous customers, someone using a web-based retailer (e.g. SLExchange) whilst offline etc. In the latter two cases, a potential solution of just indicating that the offer failed to the sender would not be sufficient.

Ideally inventory offers should work differently to IMs and not be capped even if IMs and Group notices are capped.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Argent Stonecutter added a comment - 17/May/08 09:42 AM
Yes, fix this, this is definitely a bug.

Felix Oxide added a comment - 17/May/08 07:53 PM
This bug happens to me a lot. Got my vote.

Domchi Underwood added a comment - 28/May/08 03:06 PM
Increasing priority to critical. This definitely is "inventory loss" issue.

Darien Caldwell added a comment - 28/May/08 03:25 PM
After the discussion about this on SLDev, I've been watching my offlines and noting which items arrive, and which don't once I log in.

The assertion was made that items offered by people arrive, and items offered by objects do not, and I believe this to be true. Every case of an item vanishing so far has been an item arriving from an object.

I also noticed this post recently in the SecondLife Forums talking about Busy mode, the observations about how items given behave when in busy mode also shows the same symptoms: Items sent by avatars went to the trash, Items sent by objects vanished without a trace.

http://forums.secondlife.com/showpost.php?p=2006553&postcount=16


Haravikk Mistral added a comment - 28/May/08 04:23 PM
Really what we need is a special queue for inventory transfers on the server side, with repeated requests to give the same item being discarded. Then this can be exposed within the viewer so you can view all transfers you missed due to being offline, or in busy-mode, or which you received online but didn't not accept/decline. Implementing this shouldn't be a big deal since transactions are already tracked somewhere anyway, this may even provide a way to offload a ton of them to a different "pending transactions" service.

They can easily be culled if the transaction doesn't get accepted after some amount of time, in which case the item is returned to the avatar (if it was no-copy). Could even potentially allow you to cancel a no-copy transaction if you realise you've sent it to the wrong person.


Mosley Sperber added a comment - 10/Apr/09 12:56 PM
I believe this also relates to SVC-1997 (adding this to Relates once I figure out how )

Rodgers Beardmore added a comment - 21/May/09 01:05 PM
added SVC-2915 as related. Deals with communication.

Both commerce and communication are vital to the SL experience.


Kaitlin Drechsler added a comment - 25/Oct/09 10:06 PM
I agree, this is certainly a critical issue and can be considered nothing less than inventory loss. Not only do items fail to deliver, but I've noticed some days, even if I do get the message items are sent, when I click to accept them, they disappear.


DBDigital Epsilon added a comment - 25/Nov/09 09:41 AM - edited
I have also done experiments and, while at one point if inventory was sent and IM's were capped, the inventory was not lost. However you didn't get a confirm dialog, it was just in inventory. Now though (I am not sure when this changed, probably sometime this year) inventory offers do indeed fail if IM's are capped. I did a bit of testing and it appears that after 20 IM's they are capped (although in one experiment I was able to send 23 items) and nothing appears in inventory.

This is indeed a very bad bug and needs attention. No copy object transfers can fail, and with Christmas fast approaching, many items are likely to be lost.

I agree with Haravikk, if items are not picked up after a certain period of time, they should be returned. However this could also be a problem with send via script via a subscription list. Unless the "return" message was ignored if sent via script. Otherwise the owner of the sending object could be capped very very quickly.

Another possibility, is adding a "offline" system folder to inventory that receives the items if ones IM's are capped. Then it would be easy to go though them.

Personally, I think IM's should not be capped (if at all) unless after a set period of time. Say 30 days. As per https://jira.secondlife.com/browse/SVC-2915 However inventory offers, I don't think should ever be capped and should go to say a "offline" system folder if capping does occur as stated above.


DBDigital Epsilon added a comment - 25/Nov/09 05:56 PM
Upon further investigation I find that at least the inventory loss due to IM Capping does not apply to returns. Due to the nature of everything appearing to though the IM system, I was concerned that this also applied to object returns. Thankfully it does not. Returns still make it to lost and found even if IM's have been capped.

Which makes me wonder why the rest of inventory is not handled the same way? If the IM's are capped just send everything to the Lost and Found folder? It seems this would be rather easy to implement compared to setting up a new system, also since most people check their lost and found first upon logging on it would be a easy adjustment for them.


Peter Stindberg added a comment - 25/Nov/09 10:51 PM
I think you simply were lucky during your tests. I personally have lost inventory during an object return while I was even logged in! My landlady back then did some uncautious parameter setting with the land I was on, and suddenly half of the sim got returned to the various owners. And some items (especially an expensive no-copy Lucky Chair) were nowehere to be found. And yes, I went to a sandbox and unpacked all the coalesced objects individually. Only a sim rollback which she requested got all the lost items back.

During another case while I was offline (and uncapped) I got a whole bunch of "... returned by sim onwer" offline IM's, and not a single object, not even a coalesced one, were to be found in my inventory!

From my experience returns are even more prone to loss than regular object transfers.


DBDigital Epsilon added a comment - 26/Nov/09 08:39 AM
Well a entire sim being returned at once...that is to be expected. Mass returns are rarely 100% I admit. My tests were with single one-item-at-a-time return. I don't doubt that It can still happen. SL is anything but reliable however it is not every time was my point. Compared to if you send a inventory offer object to someone that is IM capped.

Oh one other fact/experience about returns, especially if one is online. If they don't show up, clear cache and relog. I have had many items not show up in lost and found even though I was online at the time but after a relog/cache clear they were there. I am sure that Peter tried this, but I mention it for completeness.


Roberta Messerchmitt added a comment - 29/Nov/09 05:27 AM
When I loged in today all of the attachments on my IM's opened, but EVERY ONE of my Midnight Mania deliveries failed without any indication except that they did not appear in inventory anywhere. There was no time for a timeout or anything though it acted like it did, usually when they are capped or something the accept notice does not even come up.

If MM's keep failing for enough people (and there seems to be a trend for that to happen more and more) it will be a disaster for shops since people will stop going there to slap the boards (and often buy something else they see).


Peter Stindberg added a comment - 11/Dec/09 02:11 AM
Just to make the implications clear again. If your IM's are capped - the following things WILL fail:
  • XStreet SL deliveries
  • Mindight Mania boards
  • Designer Showcase Network deliveries
  • Subscribe-o-Matic deliveries
  • Hippo-Group deliveries
  • Deliverator deliveries
  • 3rd party web marketplace deliveries
  • Magazine vendor deliveries
  • Product Update deliveries (e.g. Hippo Update)

and ANY other scripted object using llGiveInventory to send you items. All these delivieres WILL FAIL when your IM's are capped.