| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Oh nice, I was worried you abandoned the PR ;) |
Sorry, something went wrong.
|
To whom it may concern: ember builder doesn't have an option for a specific execution context, so test request handling is not in the global one as it was before. It seems like race conditions are observed when dealing with some web-socket tests. |
Sorry, something went wrong.
|
@ivan-klass sorry for the delay - the global EC was used before only because it was the easiest one to obtain ;). I don't think there's anything in the tests that would rely on the global one being used: each server should be independent anyway, regardless on the thread pool on which tasks/futures are scheduled. So I would look for causes of the exceptions elsewhere, unfortunately. |
Sorry, something went wrong.
|
Then there might be a bug in http4-ember then... I'll try to dig in and reproduce when I have time |
Sorry, something went wrong.
Replace the blaze server/client backend with ember across the http4s modules, examples, docs, and perf tests. Includes connection idle timeout handling, websocket pong/close-frame fixes, multipart decoding fix, and test interpreter cleanup using ember's default idle timeout.
|
I hope I've found the underlying problem - http4s/http4s#7882 |
Sorry, something went wrong.
|
@ivan-klass ah nice, would be great to have this merged :) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Ember seems to be more modern and especially better supported in terms of cross-platform builds