-
Notifications
You must be signed in to change notification settings - Fork 378
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
Traceback when PFS returns non-JSON data #4174
Comments
The problem seems to be that @konradkonrad found out that |
Sigh... So I guess we have three options:
This should be in order of least to most annoying / ugly. |
should we go with 1 and I make a commit with find and replace? |
And we might want to tell the
|
is this another solution to the 3 solutions provided by @ulope or something you would do in addition? |
In addition, but there's not much activity on that repo, so I guess chances are small to get that fix in fast. |
Getting similar error once again.
|
Yeah, we know the reason for this, but haven't decided on a solution yet. |
This happened because the reverse proxy started before the PFS and returned bad gateway. |
Should perhaps have error handling?
The text was updated successfully, but these errors were encountered: