-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
/api/games/user/{username} crashes #15885
Comments
Probably related too : lichess-org/api#366 |
I think lichess-org/api#366 is identical with #15866 and should be fixed by #15867 at the next deploy. |
I can confirm that after the last deploy this request still crashes and is not fixed. |
thanks for your feedback, does lichess-org/api#366 still happen? |
Filtering by Newer games always come first. |
thanks, I'll take a look later today after $work, if no one is faster! |
The /api/games/ endpoint seems to be completely dead at the moment. |
Working for me for now, at least with query |
Indeed, it seems that the
|
|
After deploying #15901, the stream still crashes in the same way.
I don't seem to be permitted to reopen the issue. |
simpler reproduction curl "https://lichess.org/api/games/user/thibault?perfType=bullet"
curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2) |
Exact URL of where the bug happened
https://lichess.org/api/games/user/ToromBot?since=1711729864000&sort=dateAsc&rated=true&perfType=rapid
Steps to reproduce the bug
curl "https://lichess.org/api/games/user/ToromBot?since=1711729864000&sort=dateAsc&rated=true&perfType=rapid"
What did you expect to happen?
Export of the requested games.
What happened instead?
curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)
Operating system
Linux
Browser and version (or alternate access method)
curl
Additional information
Maybe this has already been fixed with #15867. But since it looks different from it, I have opened a new issue.Still present after deploying #15867.
Still present after deploying #15901.
The text was updated successfully, but these errors were encountered: