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

Hurley is dead project now #3

Closed
vanitu opened this issue Aug 24, 2016 · 4 comments
Closed

Hurley is dead project now #3

vanitu opened this issue Aug 24, 2016 · 4 comments

Comments

@vanitu
Copy link
Contributor

vanitu commented Aug 24, 2016

lostisland/hurley#43

@edwardsamuel
Copy link
Owner

Yes, Hurley is a dead project. This issue has been reported in #1. Hurley is not going to be yanked as the author stated in your link.

Actually, in develop branch, I already replaced Hurley with HTTPClient. But, I have no free time for this project in the past few months.

@vanitu
Copy link
Contributor Author

vanitu commented Aug 25, 2016

Ok. closing this issue than.

@vanitu vanitu closed this as completed Aug 25, 2016
@spickermann
Copy link

Since Ruby 2.7.1 Hurley pollutes the log files by raising deprecation warnings. I wonder how are your plans to replace Hurley with HTTPClient?

@Pritilender
Copy link

And since Ruby 3 Hurley breaks this gem by raising ArgumentError: tried to create Proc object without a block. It would be great if you could release the develop branch. Or if there is some more work needed regarding usage of HTTPClient, I'd be willing to help.

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

4 participants