I'm using Puffing Billy in conjunction with Sauce Connect (and a PAC file when launching Sauce Connect) to run tests in Sauce Labs. After updating Puffing Billy to 0.11.0 recently, I was running into issues with this setup where any request would result in a 502 Bad Gateway error in the browser, because of connection error: Connection refused from Sauce Connect. I rolled Puffing Billy back to an earlier version that worked for this configuration to verify that it was an issue caused by the Puffing Billy update.
Using git bisect I tracked the root cause to the changes to the gemspec in this commit. I was able to work out that the problem only exists when updating eventmachine past version 1.0.9.1.
This change causes eventmachine to resolve to 1.0.9.1 and no higher version (next version released is 1.2.0, latest is 1.2.5 - eventmachine changelog)
Notes
There are a number of fixes in versions of eventmachine after 1.0.9.1. Further investigation should be taken into what about versions of eventmachine after 1.0.9.1 causes this issue, and how to resolve the root cause of that.
Description
I'm using Puffing Billy in conjunction with Sauce Connect (and a PAC file when launching Sauce Connect) to run tests in Sauce Labs. After updating Puffing Billy to
0.11.0
recently, I was running into issues with this setup where any request would result in a 502 Bad Gateway error in the browser, because ofconnection error: Connection refused
from Sauce Connect. I rolled Puffing Billy back to an earlier version that worked for this configuration to verify that it was an issue caused by the Puffing Billy update.Using
git bisect
I tracked the root cause to the changes to the gemspec in this commit. I was able to work out that the problem only exists when updatingeventmachine
past version1.0.9.1
.This change causes
eventmachine
to resolve to1.0.9.1
and no higher version (next version released is1.2.0
, latest is1.2.5
- eventmachine changelog)Notes
There are a number of fixes in versions of
eventmachine
after1.0.9.1
. Further investigation should be taken into what about versions ofeventmachine
after1.0.9.1
causes this issue, and how to resolve the root cause of that.References
Commit that caused the issue eventmachine changelog
Risks
Medium