Current Project: HUD7

Note ID# 1394:

User:	Lulu	Submitted:	08/10/2018
	Updated status to Assigned from New.

Note ID# 1405:

User:	Lulu	Submitted:	09/10/2018
	Updated status to In Progress from Assigned.

Note ID# 1407:

User:	Lulu	Submitted:	09/10/2018
	Updated status to Testing from In Progress.

Note ID# 1408:

User:	Lulu	Submitted:	09/10/2018
	Hey Miriam, you could test it again, and it should work, as I think the issue was with some server settings. Regardless I did improve the code in the next update, and we can test it again with the new update too.

Note ID# 1417:

User:	Miriam Himanez	Submitted:	09/10/2018
	Hi Lulu, I just did another test and it isn't working so far. I'm going to retry as soon as the update is there.

Note ID# 1418:

User:	Lulu	Submitted:	09/10/2018
	Did you test it yourself or your Owner? If the latter, can you test it and see?

Note ID# 1420:

User:	Miriam Himanez	Submitted:	10/10/2018
	My Owner did. I can't do this myself, because I'd need to boot all Owners before being able to do so. I did another test. This time I sent the keybox to Owner. As expected, the test failed like the other ones.

Note ID# 1432:

User:	Miriam Himanez	Submitted:	11/10/2018
	Since the update to Signature HUD [7.5.0-beta.3.1] the Keybox immediately crashes after having been rezzed. [14:57] LULU Key Box **REZ ME**: LULU Key Box **REZ ME** [script:LULU.keybox.lsl] Script run-time error [14:57] LULU Key Box **REZ ME**: Stack-Heap Collision Afterwards it seems to be completely dead. Even clicking it isn't possible anymore.

Note ID# 1435:

User:	Lulu	Submitted:	11/10/2018
	Try getting another Key Box?

Note ID# 1438:

User:	Miriam Himanez	Submitted:	11/10/2018
	I did several trials and only one time I used the same keybox twice. After that specific trial the keybox reacted a bit different. After the runtime error this message came up: [2018/10/11 15:25] LULU Key Box **REZ ME**: Ooops! Something's gone wrong and I can't continue. Lulu has been notified, so hopefully this will be fixed soon. Please try again later. After the message the keybox went dead like the fresh ones, I used in the other trials.

Note ID# 1444:

User:	Lulu	Submitted:	15/10/2018
	I'm sorry I simply can't reproduce any of this. All my tests worked fine. Can you try 'give keybox' to me? I should receive it offline and I'll see what happens.

Note ID# 1445:

User:	Lulu	Submitted:	15/10/2018
	Updated status to Need Info from Testing.

Note ID# 1446:

User:	Miriam Himanez	Submitted:	15/10/2018
	Hi Lulu, I've just sent you the keybox from my HUD.

Note ID# 1447:

User:	Lulu	Submitted:	15/10/2018
	Thanks Miriam, I rezzed it, everything worked perfectly and I received all the keys in under a minute. I'm just wondering whether it's SL being SL again, and you or your Owner had one of those days? Again, maybe your Owner could rez the key box in City Noir? (Did he rez it at home the other day?)

Note ID# 1448:

User:	Miriam Himanez	Submitted:	15/10/2018
	This issue is way too persistent for an sl-oddity or a bad day, I believe. The problem began nearly 3 months ago and I haven't noticed it taking a break in between. I tried it out at several locations, CITY NOIR included of course. Everywhere the keybox behaved in the way as described above. This didn't change until the [7.5.0-beta.3.1]-update. Since then the runtime-error comes up and the keybox isn't even clickable afterwards anymore. At this point, I'd like to note, that HUD [7.4.15] never has been affected by this issue at all. It's just speculation of mine but could the fact, that the keybox is working for you but not for my other keyholder, be explained by some permission-issue? If true, the keybox just works for you, because you're the creator of the system. Another explanation could be, that the data registered by the additional manual Owner-registration, which seems to be needed until this closed beta changes to an open one, has become corrupted somehow. A manual de-registration followed by a re-registration could show this, or a clue onto it at least. When I'm thinking about, how to come nearer to a solution, the following ideas come to my mind as well: - Booting Owner, submitting again and repeating the trial. I just did this (in CITY NOIR) but there wasn't any change afterwards. I'm going to copy the snippet from the log, just in case of the timestamps being useful: [2018/10/15 20:48] ... Congrats! You've been given Miriam's ℒսℓս Key Box. Learn more about how to use her ℒսℓս gear at https://lu2.me/Dom . « ｙｏｕｒ  ｅｙｅｓ  ｏｎｌｙ » [2018/10/15 20:48] Lulu's LULU Signature HUD im Besitz von Miriam Himanez. hat Ihnen folgendes übergeben 'LULU Key Box **REZ ME**' ( http://slurl.com/secondlife/CITY%20NOIR/47/27/25 ). [2018/10/15 20:48] LULU Key Box **REZ ME**: LULU Key Box **REZ ME** [script:LULU.keybox.lsl] Script run-time error [2018/10/15 20:48] LULU Key Box **REZ ME**: Stack-Heap Collision - A log/debug-routine added to the kexbox or the HUD (I'm no scripter; it's just theory of course.) enabling you to study every single command being executed, while I'm trying to get keys & leashring. - Maybe there's another tester willing to take ownership over me just for a few-keybox trials? I'd accept this. We'd have a 3rd person then, who could contribute his own experiences to the solution of this problem too. - Possibly you already could find something out just by meeting with me and being in presence during the keybox-procedere.

Note ID# 1449:

User:	Lulu	Submitted:	16/10/2018
	Hey Miriam, Thanks for the detailed report. From your experience, I believe that the particular keybox found inside your current HUD is 'borked'. I have seen this in SL before. Though everyone with 7.5-beta.3 has the same keybox (5.4.1), it appears that SL doesn't necessarily treat them the same. The script state in each instance (i.e. the one you have vs. the one I have) would be different. So for some reason which is really quite beyond me, the keybox instance in this particular HUD is 'borked' and will always fail, whoever you give it to. The solution? You need to get a new HUD (with the fresh keybox inside it). I have sent you two, just in case. That's the exact HUD that I am using to test. If you need anoth third party Owner, IM Idris Georgia. He's a Dom and a LULU Fashionista Officer and he's always willing to help subs start their Gag Training/Trials even if it's being a temporary Dom to them. He can add to this comment, or you could just report what he finds.

Note ID# 1450:

User:	Miriam Himanez	Submitted:	16/10/2018
	Hi Lulu, now I'm wearing one of the two HUDs, you've sent me and sadly it's keybox malfunctions in exactly the same way, than the one from my old HUD did before. I'm sorry but I already expected this, after having read your notice, because, as mentioned earlier, the core-problem already is 3 months old with a few changes to patched or new HUDs in the meantime. So I concluded, that one particular borked keybox / HUD can't be the cause. At this point I'd like to quote myself from my last note: "Another explanation could be, that the data registered by the additional manual Owner-registration, which seems to be needed until this closed beta changes to an open one, has become corrupted somehow. A manual de-registration followed by a re-registration could show this, or a clue onto it at least." I remember your explanation after beginning with this beta-series. You told me, that this beta is a closed one and for this reason, you'd manually need to set something on your server, whenever I accept a new Owner, for everything to work correctly. Well, there have been Owner-changes within this timespan and I didn't rush to contact you about it, so I had a bit of time to look, what might not work well, before you did the setting. It was the keybox always! It behaved exactly the same way, as it began to do generally nearly 3 months ago. This brings me to the conclusion that something has gone wrong with the manual settings of the keyholder, I had all the time, or simplified said: "Without the manual settings done on the server, the keybox haven't worked in the past. 3 months ago something happened to these settings and since then the keybox never worked again." It's just theory of course but it can't be wrong to look onto this aspect carefully, I believe.

Note ID# 1451:

User:	Lulu	Submitted:	16/10/2018
	Oh wait, are we looking at the "Script-runtime error" now (that's what I thought I was addressing), or the original "outdated" message (which has changed in HUD 7.5-beta.3)

Note ID# 1452:

User:	Miriam Himanez	Submitted:	16/10/2018
	I'm referring to both all the time. When I posted the original report [7.5-beta.3] wasn't out yet and there was no runtime-error. That one has been added by the update. I might be wrong but I suspect the same cause behind the outdated-message and the runtime-error.

Note ID# 1453:

User:	Lulu	Submitted:	16/10/2018
	Regardless, you might be on to something. I didn't know of the Owner changes, and have updated it now, that would fix the first issue. Also sent you a new HUD with a reset keybox that should hopefully fix the "Script run-time error" message.

Note ID# 1454:

User:	Miriam Himanez	Submitted:	16/10/2018
	The Keybox is working again. There's no outdated-message and no runtime-error anymore. 🙂

Note ID# 1455:

User:	Lulu	Submitted:	16/10/2018
	Glad to hear that!

Note ID# 1456:

User:	Lulu	Submitted:	16/10/2018
	Updated status to Completed from Need Info.