Relay trust settings not persisting between sessions

[Antony Fairport]

I've just recently switched from another collar system to OpenCollar.
Because I wanted to keep the collar itself I followed the OC
instructions for designers and, having stripped the object of all the
old scripts, turned it into an OC collar (using 3.501 scripts).

So far it's working as documented and as I'd expect, except for one
niggle: I'm making a point of using the relay in the collar but the
trust settings don't appear to persist from one SL session to the
next. By default it doesn't trust objects I own, neither does it trust
my owner's objects. Every time such objects are used I tell the collar
to trust the owner and, sure enough, if I just trusted owners they're
there.

But when I log out and log in again the list is empty.

I'm assuming, in the first instance, that this is related to some
mistake on my part. Can anyone suggest a good place to start to get to
the bottom of this?

Thanks.

[Satomi Ahn]

Hello Antony,

You are reporting an issue with 3.501 which is now very old (and yes I
know, 3.60x has not been released yet, but current release candidate,
3.588, looks really good).
Please grab a beta updater (they can be found in the OC temple) and
try to reproduce this behavior.

If it is still not working, please report on
http://code.google.com/p/opencollar/issues/list.
Thank you!

Regards

--
Satomi

> --
> You received this message because you are subscribed to the Google Groups "OpenCollar" group.
> To post to this group, send email to openc...@googlegroups.com.
> To unsubscribe from this group, send email to opencollar+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/opencollar?hl=en.
>
>

[Antony Fairport]

Okay, will do. I'll double-check this with an alt first (unlocking the collar for some random testing isn't an option right now) and see if I can reproduce the problem there. Assuming I can I'll do the upgrade and test again and report back.

Thanks for the speedy reply.

[Antony Fairport]

I updated to 3.588 and tried again. I seem to be getting a different effect this time. This time around it did seem to remember the trusted object owner but didn't seem to make use of the fact that it was trusted. When I got asked again -- saying I trusted the object owner again -- the object owner ended up being in the trust list twice.

A subsequent relog resulted in the same effect and, after trusting again, the object owner was now listed a third time in the trust list. Asking for the list gives this reply:

[08:17]  Antony's Collar: 1: , f979c0a5-577e-43ca-868a-e9e0d86a1631
[08:17]  Antony's Collar: 2: , f979c0a5-577e-43ca-868a-e9e0d86a1631
[08:17]  Antony's Collar: 3: , f979c0a5-577e-43ca-868a-e9e0d86a1631

So, it seems, it's retaining the information, post-upgrade, just not using it.

On 22 March 2011 12:16, Satomi Ahn <satom...@gmail.com> wrote:

[Antony Fairport]

Further update:

Not too long after I updated to the beta the full 3.6 was released so
I updated again. Even with this version I still had the non-persisting
trust problem. One difference is that it did, always, without
question, trust objects owned by my collar's owner, but that's it. On
the other hand, no amunt of telling it I trusted objects that I own
made a differcene. Doing a dump of the data shows this too:

Antony's Collar whispers:
relay=mode:726,avwhitelist:f979c0a5-577e-43ca-868a-e9e0d86a1631/
f979c0a5-577e-43ca-868a-e9e0d86a1631/f979c0a5-577e-43ca-868a-
e9e0d86a1631/f979c0a5-577e-43ca-868a-e9e0d86a1631/
f979c0a5-577e-43ca-868a-e9e0d86a1631/f979c0a5-577e-43ca-868a-
e9e0d86a1631/f979c0a5-577e-43ca-868a-e9e0d86a1631/
f979c0a5-577e-43ca-868a-e9e0d86a1631/f979c0a5-577e-43ca-868a-
e9e0d86a1631/f979c0a5-577e-43ca-868a-e9e0d86a1631/
f979c0a5-577e-43ca-868a-e9e0d86a1631/f979c0a5-577e-43ca-868a-
e9e0d86a1631/f979c0a5-577e-43ca-868a-e9e0d86a1631/
f979c0a5-577e-43ca-868a-e9e0d86a1631/f979c0a5-577e-43ca-868a-
e9e0d86a1631/f979c0a5-577e-43ca-868a-e9e0d86a1631/
f979c0a5-577e-43ca-868a-e9e0d86a1631/f979c0a5-577e-43ca-868a-
e9e0d86a1631,avwhitelistnames:Antony Fairport/Antony Fairport/Antony
Fairport/Antony Fairport/Antony Fairport/Antony Fairport/Antony
Fairport/Antony Fairport/Antony Fairport/Antony Fairport/Antony
Fairport/Antony Fairport/Antony Fairport/Antony Fairport/Antony
Fairport/Antony Fairport/Antony Fairport/Antony Fairport

It seems there's an ever-growing list of the same entry (shouldn't the
whitelist feature at least check for duplicate entries?).

And then, today, many weeks after the upgrade to 3.6, I logged in to
find that the relay had stopped working. The menu button had
disappeared and calls to 'afrelay' go ignored. I did try a script
reset (from the menu) and that resulted in a script error being
thrown:

Antony's Collar: Antony's Collar [script:OpenCollar - rlvrelay -
3.581] Script run-time error
Antony's Collar: Stack-Heap Collision

On Mar 22, 4:26 pm, Antony Fairport <antony.fairp...@gmail.com> wrote:
> I updated to 3.588 and tried again. I seem to be getting a different effect
> this time. This time around it did seem to remember the trusted object owner
> but didn't seem to make use of the fact that it was trusted. When I got
> asked again -- saying I trusted the object owner again -- the object owner
> ended up being in the trust list twice.
>
> A subsequent relog resulted in the same effect and, after trusting again,
> the object owner was now listed a third time in the trust list. Asking for
> the list gives this reply:
>
> [08:17]  Antony's Collar: 1: , f979c0a5-577e-43ca-868a-e9e0d86a1631
> [08:17]  Antony's Collar: 2: , f979c0a5-577e-43ca-868a-e9e0d86a1631
> [08:17]  Antony's Collar: 3: , f979c0a5-577e-43ca-868a-e9e0d86a1631
>
> So, it seems, it's retaining the information, post-upgrade, just not using
> it.
>

> On 22 March 2011 12:16, Satomi Ahn <satomi....@gmail.com> wrote:
>
> > Hello Antony,
>
> > You are reporting an issue with 3.501 which is now very old (and yes I
> > know,  3.60x has not been released yet, but current release candidate,
> > 3.588, looks really good).
> > Please grab a beta updater (they can be found in the OC temple) and
> > try to reproduce this behavior.
>
> > If it is still not working, please report on
> >http://code.google.com/p/opencollar/issues/list.
> > Thank you!
>
> > Regards
>
> > --
> > Satomi
>