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.

Sign up for GitHub

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

Jump to bottom

Fix issue with HttpAsyncClient blocking after the first post / after opening two get streams #2

Open
marvk opened this issue Mar 12, 2019 · 0 comments
Open

Fix issue with HttpAsyncClient blocking after the first post / after opening two get streams #2

marvk opened this issue Mar 12, 2019 · 0 comments
Assignees
@marvk
Labels
bug Something isn't working Lichess API

Comments

@marvk
Copy link
Owner

marvk commented Mar 12, 2019

HttpAsyncClient seems to be never sending requests after some requests have been send. This is possibly due to a threading issue.

For example, after opening the event stream, then accepting a game via POST and opening the game stream, POSTed moves will not be send. As soon as the game stream is closed, e.g. via forfeiting the game on lichess, the request comes through (with a 400 status code).
@marvk marvk added the bug Something isn't working label Mar 12, 2019
@marvk marvk self-assigned this Mar 12, 2019
marvk referenced this issue Mar 12, 2019
@marvk
Moves are not calculated for opponent anymore, one HttpAsyncClient pe…
d3f83e7 
…r game (for now) because of the blocking issue
marvk referenced this issue Mar 12, 2019
@marvk
Workaround with second HttpClient for AsyncHttpClient deadlock
be289ae
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marvk marvk

Labels
bug Something isn't working Lichess API
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@marvk