search

OpenCollarTeam / OpenCollar

Other
121 stars 127 forks source link

Output of settings print can be unparsable under strange conditions. #951

Open scwoods1947 opened 1 year ago

scwoods1947 commented 1 year ago

What version of OpenCollar are you using? 8.2.300

What behavior did you expect? That the output of setting>print would work in a settings NC

What behavior did you see instead? If you have more that 6 owners, the auth=owner~ uuid list ends up with the 7th uuid truncated and the remainder is places on a auth+owner~ which makes the whole bunch unparseable.

What steps does someone need to take to reproduce the problem? Add 7 owners, print settings and try to add the result auth=owner strings to a settings. NC unusable strings.txt](https://github.com/OpenCollarTeam/OpenCollar/files/11368046/OC.unusable.strings.txt)

Medea-Destiny commented 1 year ago

The idea here is that the auth+owner token gets added to the string generated from the auth=owner token, so the broken UUID is no longer broken after concatenation. Have you observed any issues caused here other than being a bit hard to read?

scwoods1947 commented 1 year ago

Yes, the list is not correct it's missing two people but has three lines The viewer interprets the strings this is from chat.txt using notepad++ Access List: Owners: secondlife:///app/agent/65c1c63d-8aaa-4a5c-8314-38d324efbb1a/about secondlife:///app/agent/ea0ccd44-894e-4b52-b564-6c86b652b29e/about secondlife:///app/agent/0e5dc170-4485-49c3-8578-6d9da2f742e2/about secondlife:///app/agent/179af4bc-4851-44cc-9c61-9fa08fe54df6/about secondlife:///app/agent/ba72a1e0-0a64-4841-9ed1-d8782f02ffb0/about secondlife:///app/agent/0c15ffa7-89a7-45ae-9a63-abb7be78c117/about secondlife:///app/agent/82836db8-7e41-4627-972/about secondlife:///app/agent/c-3e8001de6c2c/about

On 5/3/23, Medea-Destiny @.***> wrote:

The idea here is that the auth+owner token gets added to the string generated from the auth=owner token, so the broken UUID is no longer broken after concatenation. Have you observed any issues caused here other than being a bit hard to read?

-- Reply to this email directly or view it on GitHub: https://github.com/OpenCollarTeam/OpenCollar/issues/951#issuecomment-1534037646 You are receiving this because you authored the thread.

Message ID: @.***>