secondlife / secondlife/viewer
[SL-18775] viewer - user search - Avatar picker doesn't perform aggregation via pagination for long result lists
@Steeltoe-Linden is already working on this.
Since Jun 10, 2024.
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
[ I'm going through my old archived, still-open Jiras and cloning them into suitable repositories. I'm not certain this was fixed by the WENG Jira work so this may just be a check-and-close situation. ]
From jira-archive-internal created by sl-service-account: secondlife/jira-archive-internal#69031
Related to SL-18774, a user managed to get the user name 'G Starchild' (first name 'G', last name 'Starchild'). In-viewer searches, for example, adding a user to the block list, fail in various ways. The one reporting here is that a search on 'starchild' would produce a list of users but not the desired one. The problem is that the search is using pagination and would only query for the first 100 results. This particular user shows up in the [101..200] range and the viewer never fills out the search result.
This may be the result of some sort of tradeoff between continuous, fast interactive searches versus a final wait-and-see fillout but that latter bit never happens.
Links
Related
Original Jira Fields
| Field | Value |
|---|---|
| Issue | SL-18775 |
| Summary | viewer - user search - Avatar picker doesn't perform aggregation via pagination for long result lists |
| Type | Bug |
| Priority | Major |
| Status | Open |
| Resolution | Unresolved |
| Components | Viewer |
| Labels | ui |
| Reporter | Monty Linden (monty.linden) |
| Assignee | Steeltoe Linden (steeltoe.linden) |
| Created at | 2022-12-02T17:31:34Z |
| Updated at | 2023-07-28T17:56:56Z |
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
'Date of First Response': '2022-12-06T20:32:35.482-0600',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'Target Viewer Version': 'viewer-development',
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.