Aditya Prakash

> I am experiencing the same bug. [same three](https://github.com/rubygems/rubygems.org/runs/3384049699#step:7:1547) :v: . It is related to changes introduced in this PR https://github.com/elastic/elasticsearch-rails/pull/999 Updating to elasticsearch 7.14 fixes this error, however now...

I just want to voice my support for this. It broke our deployments after update of shipit-engine. krane is not usable with activesupport 7.

you can upload the coverage folder using `actions/upload-artifact@v2` and use a `workflow_run` (which has access to github secrets) to upload report to codeclimate. this will work with forks and keep...

bundler-site repo https://github.com/rubygems/bundler-site would be a more appropriate place for this issue. You are also welcome to update the doc and send PR to the repo directly.

Hi, I am not sure if the fix in Socket.tcp is supposed to resolve the issue reported https://bugs.ruby-lang.org/issues/15628. `ruby -rnet/http -e "Net::HTTP.get(URI('http://example.com:8000'))"` doesn't fallback to ipv4 with this patch applied....

I would argue we don't need to spend any effort here. AFAIU, it is not a requirement that every gem uploaded to rg.org has to be installable. Consider, https://rubygems.org/gems/ims-lti/versions/1.0.1, ruby-deug...

I am putting this on owner because the gemspec has incorrect format. I understand it is most likely that this broken gem exists because of rubyforge to gemcutter migration.

> fixing things in the right place. I am not so sure about yanking a gem because it is uninstallable, it would be inconsistent with our policy of allowing other...

hey, can you help me recreate this issue? I have following in `hello_world.js.jsx`: ``` Js var HelloWorld = React.createClass({ render: function(){ return (Helloooooo World); } }); ``` My following tests...