Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EventMachine 1.1.4 breaks certain puffing-billy requests #164

Closed
asafbrukarz opened this issue Jul 5, 2016 · 19 comments
Closed

EventMachine 1.1.4 breaks certain puffing-billy requests #164

asafbrukarz opened this issue Jul 5, 2016 · 19 comments

Comments

@asafbrukarz
Copy link

A change made to the default request compressing in em-http-request (igrigorik/em-http-request@8c72228) has broken certain puffing billy requests for us.

This took a long time to diagnose, but when requests are made to load Google maps from the client, //maps.googleapis.com/maps/api/js?v=3.exp&callback=... the proxy returns a 0 length response.

Locking em-http-request to 1.1.3 fixes this issue. Any thoughts?

@ronwsmith
Copy link
Collaborator

Let's pin the version for now until someone has time to investigate further. Can you PR that?

asafbrukarz pushed a commit to asafbrukarz/puffing-billy that referenced this issue Jul 6, 2016
@damned
Copy link

damned commented Jul 19, 2016

just issued a pull request to a potential fix for this: #167

build now seems to work against em-http-request 1.1.4, 1.1.5 - previously these versions were failing the puffing billy build for me.

@ronwsmith
Copy link
Collaborator

@asafbrukarz does the PR from @damned fix the issue you were seeing?

@ronwsmith
Copy link
Collaborator

@asafbrukarz any update here?

@AlanFoster
Copy link
Contributor

We're hitting unexpected errors, potentially related to this issue. Any updates would be good 👍

@ronwsmith
Copy link
Collaborator

@AlanFoster can you try the fix in this PR: #167 If it works, I'll get it merged in soon.

@rogerkk
Copy link

rogerkk commented Mar 15, 2017

I'm sorry if this is not the best place to post this question, but I'm struggling with getting puffing-billy installed and stumbled upon this issue. Perhaps any answer to my question can help someone else with the same issue:

The puffing-billy master branch (and the 0.9.2 gem) seems to be pinned to eventmachine ~> 1.0.4, but I have other gems depending on a more recent version of eventmachine.

This issue mentions eventmachine 1.1.4, but could someone help me understand how I even get to install puffing-billy with that (or more recent) versions of eventmachine?

@ronwsmith
Copy link
Collaborator

@rogerkk try using the branch from PR #167 and see if that works for you.

@hisenb3rg
Copy link

@ronwsmith Any idea when #167 can be merged? I have similar issue with billy as @rogerkk, have other gems depending on newer version of eventmachine...

@ronwsmith
Copy link
Collaborator

@jurglic have you tried using that branch to verify it works before I merge it?

@hisenb3rg
Copy link

@ronwsmith Yes I'm using this branch. Additionally I've bumped addressable to 2.5.0 and eventmachine to 1.2.3 (bb87529).

All works for me.

@ronwsmith
Copy link
Collaborator

@jurglic Great, thanks for verifying! Can you create a PR with those two updated gems and this change?

@hisenb3rg
Copy link

Sure, will do

@ronwsmith
Copy link
Collaborator

I lot has changed around gems since this PR was opened.

Are people still having the same issues using 0.12.0?

@dmitry
Copy link

dmitry commented Feb 7, 2018

Probably a good idea would be to close this issue, as it seems eventmachine was updated to a lot newer version, so it might be solved.

@ronwsmith
Copy link
Collaborator

Feel free to reopen if anything comes up

@dreyks
Copy link

dreyks commented Jun 24, 2018

Um... so, what's the current state with EM compatibility? My code already uses EM at 1.2.3 so I can't install puffing-billy which is still at ~> 1.0.4
bb87529 seems not to exist in any branch anymore

@dreyks
Copy link

dreyks commented Jun 24, 2018

More info

It seems like first the em version was pinned to ~> 1.0.4 by #206 because something was breaking with em > 1.0.9.1
But in several months the requirement was pinned to 1.2.0.1 in #217 by same person @mwjeffcott
The question is Why would we pin it then if it's already past 1.0.9.1?

Also #212 pins em version back to ~> 1.0.4 presumably because of watir (which is a development dependency...) more info

@ronwsmith
Copy link
Collaborator

@dreyks feel free to open up a new PR with a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants