Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 646
    • Issues 646
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • 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
  • #2496
Closed
Open
Issue created Feb 02, 2021 by Kinetix@Kinetix

Searching URL of notice from remote system sometimes confused to user search?

Hi, I'm currently running develop (2.2.50-852-g7f078716-develop) with one cherry-pick 60b46540

I'm trying to search for a status from another pleroma system running 2.2.2, but the search is confused about what it's trying to receive, and doesn't pull in the status.

The status in question is: https://moc.d-x-b.com/notice/A3qJoFl4DCVzV9aZsG

I do have a few pages of debug logs - the most interesting thing I can see is:

Feb 02 20:33:55 Multibox1 mycrowd[3069]: [debug] Fetching object https://moc.d-x-b.com/notice/A3qJoFl4DCVzV9aZsG via AP
Feb 02 20:33:55 Multibox1 mycrowd[3069]: [debug] Could not decode user at fetch https://moc.d-x-b.com/notice/A3qJoFl4DCVzV9aZsG, "Object has been deleted"

I get the same result from another instance running 2.2.2, pleroma.com can't find the status either, just returns users it thinks must be best match.

So, wondering how this might happen, it seems to be an issue.

Assignee
Assign to
Time tracking