error/exit and client "lockup" due to bad search string (leading @) #71

Closed
opened 2017-11-14 08:21:45 +00:00 by sixohsix · 0 comments
Member

Woo, I got my dev instance running!

I tried to search for my masto account by typing this in the search bar:

@sixohsix@icosahedron.website

This appeared in the logs:

[error] #PID<0.698.0> running Pleroma.Web.Endpoint terminated
Server: xxx:4000 (http)
Request: GET /api/externalprofile/show.json?profileurl=@sixohsix@icosahedron.website
** (exit) :badarg

And the search bar spinner never stopped spinning. I later realized that I had to drop the leading @.

Would be nice to detect and drop the leading @ automatically rather than failing.

Woo, I got my dev instance running! I tried to search for my masto account by typing this in the search bar: `@sixohsix@icosahedron.website` This appeared in the logs: ``` [error] #PID<0.698.0> running Pleroma.Web.Endpoint terminated Server: xxx:4000 (http) Request: GET /api/externalprofile/show.json?profileurl=@sixohsix@icosahedron.website ** (exit) :badarg ``` And the search bar spinner never stopped spinning. I later realized that I had to drop the leading @. Would be nice to detect and drop the leading @ automatically rather than failing.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma#71
No description provided.