James O'Cull

I can try to check this out in 2.x - it may not be an issue in the new versions, but was an issue in the current stable.

@thecodejunkie Alright, so here's what I turned up: - The latest revision `master` is all good, it benchmarks just fine - The latest on pre-release on nuget `2.0.0-clinteastwood` has the...

I am seeing this too, but I'm not familiar enough with macOS to know how to debug. What can I do to help?

Hmmm, [following the comment trail](https://github.com/quasarframework/quasar-cli/issues/97#issuecomment-380790806) linked above I was able to see that using `wait: true` does not cause this behavior. It's worth noting that I had my timeouts set...

Can confirm - behavior is "ok" (not great) if the timeout is short. CPU is still going to jump, but it will return to normal once the time expires and...

> Aha, @nfam I think I spotted the config problem. > > instead of > > ``` > lighthouse: > am_lighthouse: false > interval: 60 > hosts: > - "LIGHTHOUSE_PUBLIC_IP"...

That was not a fix - I had it configured like this already. After more testing I think what I have is hole punching issue with my NAT. - The...

It seems to work as long as you consistently use `ArrayBuffer` and related views on both sides. If you send [a `Buffer` type from Node](https://nodejs.org/api/buffer.html) something seems to get crossed...

My team is also encountering this problem. The investigation we have done seems to indicate that connections leased from the pool are mishandled in `org.apache.http.impl.execchain.MainClientExec#execute` If the process is interrupted...

Great information to have - I was not aware of that :) Feel free to close issue in this case or re-open as something more appropriate. Thanks for the response!