Release is desperately needed #57

DanielVartanov · 2016-07-04T16:32:37Z

The last version 1.3.0 was released in year 2010, 6 years ago!
People needed to pull down changes which were made since that.

Please please please bump up and release a new version.

The text was updated successfully, but these errors were encountered:

glebm · 2017-03-10T15:59:35Z

The maintainer of this gem hasn't been active on Github since 2014 and hasn't tweeted nor instagram'd, nor flickr'd anything since November 2015. His homepage and blog are gone as well.

DanielVartanov · 2017-03-10T16:09:58Z

@glebm oh god, are you assuming the worst? Let's hope it's not the case. But someone needs to take over maintenance anyway. I really don't want to undertake for this task as I'll won't devote enough time for the project, but what would you suggest for such case? Is there a common protocol in the community?

glebm · 2017-03-10T16:22:08Z

oh god, are you assuming the worst?

Not necessarily, as he also seems to have a history of quitting the internet: https://twitter.com/robolson/status/667436321812701189

Is there a common protocol in the community?

Usually, an org that uses the gem heavily and is willing to maintain it forks the repo, emails rubygems explaining the situation to get ownership of the gem, and contacts github to set the new repo as the canonical one. There are several precedents, such as rake.

DanielVartanov · 2017-03-11T18:26:39Z

@glebm great, huge thanks for explanation

betesh · 2017-03-23T16:13:58Z

Usually, an org that uses the gem heavily and is willing to maintain it forks the repo, emails rubygems explaining the situation to get ownership of the gem, and contacts github to set the new repo as the canonical one. There are several precedents, such as rake.

Has anyone done that yet?

betesh · 2017-03-31T15:30:09Z

@technicalpickles @MarkMenard @mislav @blaine @jacqui @myronmarston @kachick @illuminerdi @syborg @trevorrowe @larrytheliquid @chrisZingel @josh @Empact @akahn @chubas @anselmoalves

All of you have contributed to this gem in the past. If any of you are interested in maintaining it, please let us know by commenting on this issue. Once one of you has volunteered and there is agreement among contributors about who will take on this role, we can then reach out to rubygems and github to let them know that there is a new maintainer.

betesh · 2017-04-20T18:05:01Z

Since nobody else has spoken up, I will be reaching out to github and rubygems

Empact · 2017-04-20T19:01:45Z

@betesh FYI I use webmock for current projects.
https://github.com/bblimke/webmock

chrisk · 2017-06-10T22:46:12Z

Hi all, thank you for posting. I'm really sorry for leaving you hanging for so long.

When I last worked on this project, I was very sick. It eventually got serious enough that I had to stop working, pack up my apartment in San Francisco, and move home, putting my life on hold completely.

Thankfully, I eventually made it through, and I'm doing much, much better these days.

Back when I was first starting to get better, I decided to fill the newly available hours of the day with activities I thought would help shore up my physical and mental health. I started exercising again, joined a choir, started getting fluent in Spanish again, got a skateboard, started volunteering, and on and on. I spent a lot of time caring for my mother after she got sick herself and ended up in the hospital. These days, of all things, I actually get paid to sing in a professional vocal group sometimes. It's been a strange & winding path, but one I needed to walk.

All through this, I wasn't paying attention to this project, nor responding to a lot of friends who were concerned about me. I think I was pretty burned out in addition to being sick, and just wasn't ready to deal with the responsibility of working on this again, or of maintaining those relationships. So I put it all off. In hindsight, I think that was probably a healthy defense mechanism for me, but I wish I had let all of you know what was happening. Not least of all @blaine, who started this project and graciously let me start maintaining it way back in 2008. I apologize for that. I know lots of people use FakeWeb to make important things, and it's not unreasonable to expect a minimum level of communication to reciprocate your investment in a tool.

With all that out of the way, I'm here to say that I'm going to take up maintaining FakeWeb once again. You can expect a point release to restore compatibility with all current mainstream versions of Ruby. After that, I'll start on the rest of the open pull requests.

I just got a new Mac, so I'm currently setting up my environment. After I finish that you should start seeing activity on this project again.

If you need something in the meantime, certainly try WebMock and see if it works for you. That project actually started as a copy-and-paste of FakeWeb, oddly enough, although it has developed considerably since then. And if you've already switched and it works for you, then great.

Going forward, I think it's important for FakeWeb to continue to exist so that we always have a small, simple, fast tool for the 99% case of just testing code that uses Net::HTTP. Also, the gem has been an inspiration (and a template) for library authors in many other languages over the years, and that's been good for software development everywhere. I'd like to keep that going.

Okay. Whew. Thanks for reading all that, and thank you all again for your concern. If you have a fix to contribute, please do continue to open/update issues/pull requests and I'll merge. Updates should post here as I reference this ticket in commits. Onwards!

--Chris

@strzibny

Thanks for reporting: @strzibny in #48, @ggilder in #50, @davidcornu in #58, and @SamMolokanov in #60. References #57.

This fixes a deprecation warning: simplecov_formatter_class: [DEPRECATION] ::[] is deprecated. Use ::new instead. References #57.

@davidcornu

Checking the exit status of `command -v` should pretty much work everywhere. See e.g. https://stackoverflow.com/a/677212/54401 for a discussion. Thanks to @davidcornu for reporting this and suggesting an alternate fix in #58. References #57.

* add-new-argument-check: Simplify test by removing irrelevant fixture Tests: fix URI to really be invalid for Ruby 2.2 Raise if .register_uri isn't given an options hash Closes #53. References #57.

@zeha

* update-net-http-mocks-for-ruby-2.3: Add explanatory comment to test helper net/http uses connect_nonblock since 2.3.0 Thanks to @zeha for patching this in #56, and also to @davidcornu for the version in #58. This gets us all green on MRI Ruby 2.3 and below. Closes #56. References #57.

@voxik

Background: 1. As of Ruby 2.2, calling #close on a socket that's already closed no longer raises an exception. 2. As of Ruby 2.4, Net::HTTP no longer checks #closed? every time before calling #close on a socket, since there's no longer any danger it will raise. See: * r56795 (ruby/ruby@6394b63db9abe34234e7) * r56865 (ruby/ruby@f845a9ef76c0195254de) FakeWeb's internal StubSocket has been short-circuiting those pre-2.4 checks by just always returning true when #closed? is checked, preventing #close from ever being called. Now that the checks are gone, StubSocket needs its own #close method. This fixes a variety of NoMethodErrors on Ruby 2.4, but is basically backwards-compatible with earlier implementations. (When running on pre-Ruby 2.2, I suppose StubSocket should raise when you call #close on an already-closed socket. I'll look into that, but all our functional tests are passing on earlier Rubies at the moment.) While we're at it, I changed #closed? to stop just always returning true, to be closer to how the Ruby stdlib's sockets behave. This doesn't appear to break anything but I'll revert that part if I find anything in the relevant Net::HTTP code that conflicts. Thanks for reporting and submitting patches: @voxik in #59, @SamMolokanov in #60. Closes #59. References #57.

* add-stub-socket-close: Change stub socket for Ruby 2.4 compat Rename test class References #57.

* jruby-updates: Tests: modernize JRuby runtime configuration Tests: JRuby now bundles its OpenSSL gem This gets everything working on JRuby 9000. References #57.

* update-dev-deps-for-old-ruby-compat: Tests: just skip coverage on Ruby 1.9.0-1.9.2 Hold back RDoc version on Ruby 1.9.2 and earlier Tests: fix a spurious failure on 1.8.7 Tests: bump compatible Rubies to the latest Rake Reorganize the dev. dependencies in the gemspec Reformat comments in gemspec References #57.

* update-bufferedio-method-signature-for-24-compat: Update Net::BufferedIO patch for Ruby 2.4-compat Extract-method refactor Refernces #57 and #60.

chrisk · 2017-07-17T01:41:25Z

Hello everyone!

I've got a ton of fixes merged now, and as far as I know we're code-complete to release 1.3.1. I still need to update the docs and write up a changelog. In the interim, if there's anybody out there who could test FakeWeb in their projects, I'd appreciate it. The master branch should be compatible with all versions of MRI from the past decade or so (Ruby 1.8.6 or later, up to 2.4.x), as well as recent versions of JRuby and Rubinius.

You can try the current master branch by doing something like this in your Gemfile:

group :test do
  gem "fakeweb", github: "chrisk/fakeweb", branch: "master"
end

sdsykes · 2017-07-17T08:33:41Z

I can confirm tests run ok on ruby 2.4.1 in https://github.com/sdsykes/fastimage with the latest changes. Thanks!

choonkeat · 2017-08-02T00:56:47Z

Perhaps a release candidate gem? Not all environments are hospitable to installing gems by git

thewoolleyman · 2017-08-28T23:56:37Z

@chrisk Please publish a prerelease gem to rubygems. Otherwise, your latest updates cannot be used as a gemspec development dependency for other gems.

esbanarango · 2018-01-17T15:20:35Z

@chrisk Thank you! Could we release 1.3.1 or at least have a prerelease gem? We can't use it in other gems like:

add_development_dependency "fakeweb", github: "chrisk/fakeweb", branch: "master"

🙏 🙏 🙏 🙏

abarrak · 2018-01-30T09:44:09Z

It'll be very helpful for the gem users to have 1.3.1 released.

esbanarango · 2018-02-12T04:38:04Z

@chrisk let me know if you need a hand here ✋ 🙏

esbanarango · 2018-04-10T03:17:40Z

1.3.1 coming soon...

sdsykes · 2018-09-10T04:55:50Z

I pushed a gem named fakeweb-fi to rubygems, built from master (version 1.3.1) - feel free to use it if you need. It has no other changes than the name of the gem and the version number - so you would still need require 'fakeweb' to load it.

It was enough to get https://github.com/sdsykes/fastimage/ passing anyway.

esbanarango · 2018-10-12T06:18:22Z

Thank you @sdsykes

- 테스트 디펜던시 `fakeweb` 동작이 깨지던 부분을 `fakeweb-fi` 모듈로 마이그레이션 (chrisk/fakeweb#57 (comment)) - `rest-client` `2.1>=` 버전에서 `gzip` `Accept-Encoding` 헤더를 제대로 처리하지 못해 반환 데이터가 제대로 잡히지 않던 현상 수정 (#4)

betesh mentioned this issue Mar 23, 2017

please tag a new version and release a new gem #47

Closed

SamMolokanov mentioned this issue Apr 6, 2017

Some fixes for ruby 2.4.1 compatibility #60

Closed

evazion mentioned this issue May 11, 2017

Test failures under ruby 2.4 danbooru/danbooru#3039

Closed

chrisk added a commit that referenced this issue Jun 13, 2017

Tests: newer Rubies need a gem to get test/unit

40af388

Thanks for reporting: @strzibny in #48, @ggilder in #50, @davidcornu in #58, and @SamMolokanov in #60. References #57.

chrisk added a commit that referenced this issue Jun 14, 2017

Merge a fix to the tests' simplecov setup from #58

6f7598b

This fixes a deprecation warning: simplecov_formatter_class: [DEPRECATION] ::[] is deprecated. Use ::new instead. References #57.

sdsykes mentioned this issue Jun 20, 2017

Add Ruby 2.4.1 to travis matrix sdsykes/fastimage#88

Closed

chrisk added a commit that referenced this issue Jun 26, 2017

Merge branch 'add-stub-socket-close'

9fde35b

* add-stub-socket-close: Change stub socket for Ruby 2.4 compat Rename test class References #57.

chrisk added a commit that referenced this issue Jun 27, 2017

Merge branch 'jruby-updates'

694429b

* jruby-updates: Tests: modernize JRuby runtime configuration Tests: JRuby now bundles its OpenSSL gem This gets everything working on JRuby 9000. References #57.

chrisk added a commit that referenced this issue Jul 9, 2017

Merge branch 'update-bufferedio-method-signature-for-24-compat'

34d018a

* update-bufferedio-method-signature-for-24-compat: Update Net::BufferedIO patch for Ruby 2.4-compat Extract-method refactor Refernces #57 and #60.

georgiana-b mentioned this issue Aug 6, 2017

Fix development and tests for Ruby 2.4 frictionlessdata/datapackage-rb#42

Closed

krisleech mentioned this issue Jan 11, 2018

Compatibility Issue with Ruby 2.4? #62

Open

This was referenced Jan 17, 2018

Waiting on: fakeweb#57 To Version 0.0.2 esbanarango/zapier-REST-hooks#6

Closed

Rails 5.1 support? esbanarango/zapier-REST-hooks#2

Closed

jarongao mentioned this issue Apr 30, 2018

Cluster start timeout error for ElasticSearch 6.2.2 elastic/elasticsearch-ruby#508

Closed

esbanarango mentioned this issue Jun 2, 2018

doesnt work on rails 5.x? esbanarango/zapier-REST-hooks#8

Closed

davidcornu mentioned this issue Apr 9, 2019

Test failures? #66

Open

alex-w-k mentioned this issue Apr 29, 2019

Recommend moving away from fakeweb gem due to compatibility issues with ruby > 2.4 ekosz/Plex-Ruby#24

Open

dilumn mentioned this issue Nov 30, 2019

Update dependency gem versions Kaligo/alipay-global#4

Open

anduong mentioned this issue Aug 17, 2021

Add API Versioning configuration Shopify/shopify_api_console#22

Merged

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Release is desperately needed #57

Release is desperately needed #57

DanielVartanov commented Jul 4, 2016

glebm commented Mar 10, 2017 •

edited

Loading

DanielVartanov commented Mar 10, 2017

glebm commented Mar 10, 2017 •

edited

Loading

DanielVartanov commented Mar 11, 2017

betesh commented Mar 23, 2017

betesh commented Mar 31, 2017

betesh commented Apr 20, 2017

Empact commented Apr 20, 2017

chrisk commented Jun 10, 2017

chrisk commented Jul 17, 2017

sdsykes commented Jul 17, 2017

choonkeat commented Aug 2, 2017

thewoolleyman commented Aug 28, 2017

esbanarango commented Jan 17, 2018

abarrak commented Jan 30, 2018 •

edited

Loading

esbanarango commented Feb 12, 2018

esbanarango commented Apr 10, 2018

sdsykes commented Sep 10, 2018

esbanarango commented Oct 12, 2018

Release is desperately needed #57

Release is desperately needed #57

Comments

DanielVartanov commented Jul 4, 2016

glebm commented Mar 10, 2017 • edited Loading

DanielVartanov commented Mar 10, 2017

glebm commented Mar 10, 2017 • edited Loading

DanielVartanov commented Mar 11, 2017

betesh commented Mar 23, 2017

betesh commented Mar 31, 2017

betesh commented Apr 20, 2017

Empact commented Apr 20, 2017

chrisk commented Jun 10, 2017

chrisk commented Jul 17, 2017

sdsykes commented Jul 17, 2017

choonkeat commented Aug 2, 2017

thewoolleyman commented Aug 28, 2017

esbanarango commented Jan 17, 2018

abarrak commented Jan 30, 2018 • edited Loading

esbanarango commented Feb 12, 2018

esbanarango commented Apr 10, 2018

sdsykes commented Sep 10, 2018

esbanarango commented Oct 12, 2018

glebm commented Mar 10, 2017 •

edited

Loading

glebm commented Mar 10, 2017 •

edited

Loading

abarrak commented Jan 30, 2018 •

edited

Loading