Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 647
    • Issues 647
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 89
    • Merge requests 89
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #2301
Closed
Open
Issue created Nov 13, 2020 by Fristi@fristi

User handle suggestions broken after 2.2 update

Environment

  • Installation type: Source
  • Pleroma version: 2.2.0-3334-g87fc069d-subcon (See: fristi/pleroma@87fc069d)
  • Elixir version: 1.10.4
  • Operating system: Devuan Beowulf 3.0
  • PostgreSQL version: 12.4 (Debian 12.4-1.pgdg90+1)

Bug description

After the running the pleroma 2.2 update, I've noticed that the handle suggestions in pleroma-fe are empty when searching for particular users (though not for all users).

firefox_EpOs5wNmYy

For instance, in the above screenshot, the user solidsanek didn't pop up as a suggestion until the entire handle has been typed in, despite this being a user I communicate with on a daily basis. Checking the requests reveals that the search query doesn't return any results until the full handle has been entered:

firefox_6K9uR09Iyk navicat_ICVAsmPBHG

After "finding" these users once, the results will be cached client-side, but these are lost after a refresh.

Using the search function also yields no user results for the same query:

firefox_k97ZArcS6c

Update: eventually the search could find users more properly again, so this mostly fixes itself given enough time, but I still wonder why it happened in the first place.

Edited Nov 13, 2020 by Fristi
Assignee
Assign to
Time tracking