Matt Hughes
Matt Hughes
Linking #6419 here since it seems there is some agreement on removing `uri`'s default value from `Request`.
I am still getting this with 0.23.3. To make it easier to test, I set my idle connection timeout to 5 seconds. Sure enough first request succeeds, wait 6 seconds,...
Not exactly sure what this fix was supposed to do, but experiencing this on a GET request. ```scala private[ember] object RetryLogic { private val retryNow = 0.seconds.some def retryUntilFresh[F[_]]: RetryPolicy[F]...
If I make that fix locally (by duplicating retry policy locally) retries seem to work fine.
Can certainly PR the fix; might need some pointers regarding the test.
Wrote this test but could use a little help. I had to put it in EmberServerSuite because ember-client doesn't have access to ember-server. Unless there is some other server backend...
Would love this as well. Above use cases ring true. I also have an issue this would solve with OpenStack server_group / anti-affinity. Scheduling 10 instances with anti-affinity in parallel...
@armanbilge 3.1.2 fixes the referenced problem. It seems like scalacheck has been updated as well. Can you summarize the current ecosystem blockers?
> Given that module splitting support has landed in 1.3, I don't think we need the `libraryOnly` mode. So I think "pull npm dependencies only" might be the right role...
@raquo Hmm why would you have requiresDOM in Test if using Selenium as your JSEnv? Doesn't the latter provide that inherently? I thought the former's role was solely to download...