llRequestUserKey() no longer returns UUID's for historical usernames.
complete
Renae Daines
Sometime in September (at least, that is when it was originally observed) the
llRequestUserKey()
started failing to return historical username UUIDs. Instead of returning a key, they instantly return with NULL_KEY
. This breaks the lookup for those who have changed their username.This behavior seems to be dependent on the username. Some usernames still return correct data, while others return with a
NULL_KEY
. For privacy purposes I can't list the usernames I have found this to be an issue with but I tested 20 different names and 40% of them return back
NULL_KEY
on known good historical names. I wasn't sure if this belonged under Server Bugs or Scripting Bugs.
Log In
Maestro Linden
Hi Renae Daines, this bug should be fixed as of this morning (~10AM SLT to be precise). I was able to confirm that the cases you supplied that were broken for me yesterday are now resolving to the correct agent_id.
This post was marked as
complete
Maestro Linden
updated the status to
tracked
Maestro Linden
updated the status to
needs info
Maestro Linden
Hi Renae Daines, I'm not seeing this issue in general - I looked up both the old and new names for a particular user who had changed their name in 2023, and
llRequestUserKey
returns the same agent_id for their prior and current names.If you're seeing this issue with particular agents, we need those specific details. You can provide their current usernames or agent_ids if you want to keep their prior names private - we can look up the prior names internally.
Renae Daines
Hello Maestro Linden,
Here's a list of UUID's that have failed in my testing.
547a4f3e-3518-42e7-ad93-7370232f32ad
06e69668-6127-45ff-b405-4de27e41c43d
8adf55db-6419-4224-b62d-427282789c94
0337bd48-ed6b-4108-bb97-57a126b49afa
2de10e69-c952-4d25-9c01-b9d37c2e8bc2
7ffb3777-b6dc-4d16-8fa5-6a7cd60712e4
95f89f0e-bc31-43cc-bceb-a68db8fb2273
Thanks!
Maestro Linden
Renae Daines: Thanks for the list of names. I went through the first 5 or so and can confirm that at least some of their past usernames don't resolve to the agent_id.
It doesn't appear that llRequestUserKey is failing to resolve past names in general, though - I looked at some other agents who had changed names multiple times, and all of their past aliases properly resolve to their agent_id.
One of the agents in your list has changed their name several times in the past, and I see that _some_ of their past aliases resolve to agent_id, but not others. Some of their older and newer names resolve properly, but some of the names in the middle do not - it's curious.
Renae Daines
Maestro Linden: It's definitely something to do with the individuals. I tested across the Main channel, LeTigre, Magnum, and BlueSteel sandbox cluster and all four report the same exact failures across a list of 100 previous names. The percentage drops to around 33% of my sample data, but that's still 33 failures on previous usernames. Some I know for a fact were only ever changed once while others I have no clue how many times they may have changed.
Renae Daines
Title really should be: llRequestUserKey() selectively returns NULL_KEY instead of UUID's for historical usernames.
But I get an "Uh-oh. Something went wrong" each attempt to edit.