Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: if the account doesn't exist on the server, EOF error is shown #4215

Open
germainelee opened this issue Feb 17, 2025 · 2 comments
Open

Comments

@germainelee
Copy link
Contributor

This error comes up when I enter the following in the input field. I can rectify my error by typing a different fedi handle, but what does that error mean? Can it be written differently so that viewers who have low technical knowledge would understand?

Note: I am not ety

Screenshot_20250109_040649_Chrome.jpg

Originally posted by @germainelee in #4103

@mahmed2000
Copy link
Contributor

Its a backend bug. The remoteFollow request triggers a webfinger request from the server. If the account doesn't exist on the server (realety@ instead of stream@ in this example), the typical response is an empty body with a 404. The backend doesn't check for this, and you get an End Of File from the json decoder trying to read empty data.

@gabek
Copy link
Member

gabek commented Feb 18, 2025

Is this specifically about the EOF error, or all errors being surfaced to users? I was under the impression the problem was we're surfacing errors to users and should instead should replace it with a generic message that is nicer looking.

@germainelee germainelee changed the title Replace "EOF" error with "There was a problem" bug: if the account doesn't exist on the server, EOF error is shown Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants