-
Notifications
You must be signed in to change notification settings - Fork 31
resolver broken in 1.1.0pre0 if used with em-resolv-replace #50
Comments
Does |
I was using Ruby’s resolve-replace for a while, maybe in all of the v1.0 releases. I stopped using it because I found cases where it didn’t work, but I can’t say for sure what they were off the top of my head. I can have a look, but I can’t promise I can make it work. |
Thanks for reporting it. I want to make sure that cql-rb doesn't interfere with other gems. |
I am not sure what is there to resolve. I am providing ip adress, it shouldn't even try to resolve it. I am using sinatra-synchrony which is loading em-resolv-replace automatically. I'll try to disable that. |
This is an experiment to see if I can get to the bottom of #50
@rubycut I've pushed up a branch called |
@iconara , I am pretty swamped at the moment, in the meantime, I removed dependency to em-resolv-replace from sinatra-synchrony, when I catch time, I'll try newest version again. I'll test your branch when I catch time, probably with next week. |
Have you had time to test this yet? |
No, I suck. Being only ruby programmer in the company, I hope you understand. |
I'll close this now, the branch I created is now hopelessly out of date. If you get the time feel free to open a new issue. |
In 1.0.5 everything was working ok, bit now it says "invalid address":
Interestingly enough, it's broken only is some cases, with provided ip, otherwise if I put localhost or 8.8.8.8 then it works.
I traced it back to here:
https://github.com/iconara/cql-rb/blob/master/lib/cql/io/connection.rb#L34
I tried using resolver by itself and it works fine.
The text was updated successfully, but these errors were encountered: