Saving scripts failing 100% of the time

As can be seen in the following screen captures, editing and saving scripts has so far failed 100%, resulting in the error messages shown each time I've tried.

I'm posting here so that other scripters will know and can provide feedback about their own experiences and whether they are also experiencing this.

http://www.daikonforge.com/scriptfail1.png
http://www.daikonforge.com/scriptfail2.png

I get this message off and on, usually during times of high database load. Try again later when the mad rush to log back into SL abates.

Um, yeah, this is funny and sad at the same time....

I can't report the bug, either, cause I only get this error dialog:

http://www.daikonforge.com/bugreportfail.png

Off to see if Jira's any better

Well... I certainly will do that... But since it was a problem all day yesterday and part of the day before that, I'm not too hopeful.

We know from the blog that they are goofing with the databases, so I don't have a lot of confidence that it's only a peak load issue, though I guess I will retain just a small bit of hope anyways

Oh, hell... In the process of trying it again, the object whose scripts I'm trying to edit has to all appearances ceased to exist now....

Very nice

Hehe, I'm very pleased about this, in a perverted sort of way, because I knew it was coming.

I've experienced this in the past, and I know that when the right-click pie menu loses the "Drop" option and the item no longer shows in your inventory, then to detach it results in the item disappearing forever since there is no longer a "link" to it in your inventory. Attachments are somewhat special in the sense that they are not duplicated when attached, much like a regular no-copy object is not duplicated when rezzed, even if it is a copy-enabled object or you are the object's creator.

Since this has happened before, I had the foresight this time to edit the object while still having it attached, and changed the name to "MISSING SWORD" before detaching it. I did this for two reasons: First, it would make it very easy indeed to search my inventory for that object, being a unique name (I did, it's gone); Second, it might allow someone at LL to look for an orphaned asset in the database with that name, perhaps being useful in diagnosing the issue.


.

Nice idea, assuming the changed name ever makes it to the database...