Alert: ANOTHER llGiveInventory problem; vendor users / web sellers beware!

In the 15 months I've been running SLBoutique, I've gotten one or two messages about a resident being in busy mode and not being able to get inventory. For the past week, I've been getting 5-10 PER DAY. In talking with some residents who contacted me for customer service, it appears that Second Life is seeing the users as "Busy" even though they are NOT set to busy mode.

We've been asking to get rid of the ridiculous auto-decline for how long now? Years? And now a bug bites us in the arse. PLEASE, remove the ridiculous auto-decline while in busy mode, and fix this bug! I've seen it happen first hand.

So, vendors, please be aware this is happening. It seems like the only safe thing any more is to make every item no-transfer so replacement copies can easily be given.

Regards,

-Flip

Yuk, not another one. I guess this could be related to the problem of the system delivering IMs etc. to email when you teleport, which is really bizarre.

My thoughts exactly. While I understand these problems will most likely occur when major changes like de-centralization of communications occur, I was really hoping they'd be fixed by now. Getting a solid repro on this is going to be near-impossible, considering the wonderfully detailed message given back is subject: "Message From Second Life", with generic text akin to: "The Resident you have tried to pass inventory to has been declined." Argh.

Regards,

-Flip

This bug has been going on for how long now? And which types if vendors does it seem to affect most, say, those that pull from a central or those that are stand alones?

Sorry, I know that seems like a stupid question, but I will simply say that I have no clue what's really involved yet, since I'm still learning LSL and I was always slow on learning code.

It seems as long as no-one is in charge of telling the programmers to fix bugs this will continue. LL's policy of letting programmers choose their own work is begining to fall apart I think. The policy is a really good one and I applaud LL for it, but it only works when it's managed properly. When serious bugs build up because everyone would rather work on something "fun" it's a serious issue. Someone should be employed to asign bug fixes to the appropriate programmers for the job. When there are no more bugs, then they can choose what they want to do.

Since the last 3 updates, loads of bugs have been introduced. Building is harder, IMs don't arrive, llGiveInventory fails, and lots more, these aren't trivial they affect us all extremely negatively.

I hadn't heard this before. Is this actually true? I've never known an IT shop EVER that did that - without organization and change control, the whole system falls down around your head.


I second that. You're making kitty scared, though.

It will affect any vendor equally; the problem is with llGiveInventory and busy mode, which all vendors will be hit by. I would describe this as very widespread, but it is definitely happening. The bigger problem is that this makes sellers look bad, when in fact, its a problem with Linden Lab, both code-wise and in their auto-decline methodology.

Regards,

-Flip

It would appear to be true from talking to staff, reading staff blogs and reading various forums. I'll admit to going by hearsay though. Obviously I don't work there myself, so it's not insider knowledge.

To be honest I'd expect LL to have someone in charge, from the outside though, it doesnt appear to be the case!

I've almost given up using the bug reporter, it just feels like banging my head against the desk.

Thanks, Flipper.

This means then that not just vendors, but note card givers, land mark givers, anything that uses that particular string could be hit, too, but the vendors are the one's we'd notice most, as actually L changes hands.

Ouch. Maybe if we call support and start chanting that we want this fixed?

Right here.