Prevent eventmachine from installing 1.2.x - #206
Merged
Merged
Conversation
Collaborator
|
@mwjeffcott thanks for the contribution! |
Collaborator
|
Released in 0.11.1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.0recently, 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 refusedfrom 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 bisectI 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 updatingeventmachinepast version1.0.9.1.This change causes
eventmachineto resolve to1.0.9.1and 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
eventmachineafter1.0.9.1. Further investigation should be taken into what about versions ofeventmachineafter1.0.9.1causes this issue, and how to resolve the root cause of that.References
Commit that caused the issue
eventmachine changelog
Risks
Medium