耙释放不起作用

Question

我正在尝试发布我的 gem 运行这个命令的新版本：

rake release --trace

但是过程卡在这里：

rake release --trace
** Invoke load_app (first_time)
** Execute load_app
** Invoke release (first_time)
** Invoke build (first_time)
** Execute build
paperclip_upload 1.2.0 built to pkg/paperclip_upload-1.2.0.gem.
** Invoke release:guard_clean (first_time)
** Execute release:guard_clean
** Invoke release:source_control_push (first_time)
** Execute release:source_control_push
Tag v1.2.0 has already been created.
** Invoke release:rubygem_push (first_time)
** Execute release:rubygem_push

我尝试过但没有奏效的事情：

删除 github 标签并重新发布。
将 gem 更新到上一版本 (2.4.8) 执行 gem update --system。
重置我的 rubygems API 键。
使用api。 curl --data-binary @pkg/paperclip_upload-1.2.0.gem -H 'Authorization:XXX' https://rubygems.org/api/v1/gems

The POST is not working but I can retrieve my gems performing a GET.

使用gems

require 'rubygems'
require 'gems'

Gems.configure do |config|
  config.username = 'xxx'
  config.password = 'xxx'
end

Gems.push(File.new("pkg/paperclip_upload-1.2.0.gem"))

避免使用 rake 任务执行 gem build 然后 gem push -v pkg/paperclip_upload-1.2.0.gem 但也被卡住了：

gem push -v pkg/paperclip_upload-1.2.0.gem
GET https://rubygems.org/latest_specs.4.8.gz
302 Moved Temporarily
GET https://s3.amazonaws.com/production.s3.rubygems.org/latest_specs.4.8.gz
304 Not Modified
GET http://rubygems.org/latest_specs.4.8.gz
302 Moved Temporarily
GET http://production.s3.rubygems.org/latest_specs.4.8.gz
200 OK
GET http://rubygems.org/quick/Marshal.4.8/rubygems-update-2.4.8.gemspec.rz
302 Moved Temporarily
GET http://rubygems.global.ssl.fastly.net/quick/Marshal.4.8/rubygems-update-2.4.8.gemspec.rz
200 OK
Pushing gem to http://rubygems.org/...
POST http://rubygems.org//api/v1/gems
connection reset after 1 requests, retrying
POST http://rubygems.org//api/v1/gems
connection reset after 1 requests, retrying
ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
    too many connection resets (http://rubygems.org//api/v1/gems)

有什么线索吗？

RubyGems’ status page 对我来说都是绿色的。

Answer 1

这是我的问题How to reduce the size of a gem

尝试发送带有 585MB tmp 垃圾的 gem 不是最好的主意...

Answer 2

对我来说，在启用 2FA on Rubygems.org 之后，我无法再运行 rake release。

release:rubygem_push 步骤挂起。结果 older versions of gem don't support 2FA, and intermediate versions had a bug where the process is waiting for 2FA code entry but there's no prompt.

我的解决方案是在进程等待时输入 2FA 代码 + return。

最终您应该能够 gem update --system 获得具有完整 2FA 支持的 gem 的新版本。

耙释放不起作用

rake release does not work

gem

rubygems