Sean Glover
Sean Glover
See if the new retries introduced in #403 help with this issue. I've set the chart default value to 2 retries.
Hopefully the retries resolved the original issue. @rsommer The issue you're describing is tracked in #106.
I'll be honest, I don't have a lot of time to troubleshoot this. If you can create a reproducer in the integration tests that would help. If all else fails...
https://travis-ci.com/akka/alpakka/jobs/254015144#L413
https://travis-ci.com/akka/alpakka/jobs/260163611#L499
https://travis-ci.com/akka/alpakka/jobs/271383980#L378
https://travis-ci.com/akka/alpakka/jobs/275777751#L480
I believe it has something to do with the upgrade to the 1.x.x branch of [http-proxy](https://github.com/nodejitsu/node-http-proxy). grunt-connect-proxy 0.1.10 is using "http-proxy": "~0.10.3". There's a lot of rewritten work in the...
I've resolved this issue in my own plugin ([grunt-connect-prism](https://github.com/seglo/grunt-connect-prism)) by handling the new error event in http-proxy `1.x.x`. I was able to reproduce the bug using a user's codebase, but...
@rbrcurtis Thanks for trying. Is your project on github or can you provide me with a reliable way of reproducing the issue?