Fix gemcutter:import:process

[Earlopain]

It creates a Pusher with the first argument being a user but it expects an API key.
Similarly, the api key/user must be present in the database for validations.

Broken since #4213. With this change, I was able to import from a fresh install.

[simi]

well spotted 💪

Any particular reason to use import task even with advanced seed we have today? I had no need to use import task in last month since I'm happy seed user.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.22%. Comparing base (4c88dd6) to head (39bf502).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5198      +/-   ##
==========================================
- Coverage   96.06%   93.22%   -2.84%     
==========================================
  Files         430      430              
  Lines        9120     9179      +59     
==========================================
- Hits         8761     8557     -204     
- Misses        359      622     +263     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Earlopain]

I'm trying to understand why https://rubygems.org/gems/pry/reverse_dependencies (not the only one) shows dependencies multiple times. I can download a bunch of versions, put them in a directory to import and see what happens.

[yob]

I ran into this error while following CONTRIBUTING.md to set up a local rubygems.org dev environment for the first time today.

I hadn't seen this PR yet, so my workaround looked like this:

diff --git a/lib/tasks/gemcutter.rake b/lib/tasks/gemcutter.rake
index c2e0c6193..6ee138d8f 100644
--- a/lib/tasks/gemcutter.rake
+++ b/lib/tasks/gemcutter.rake
@@ -16,7 +16,7 @@ namespace :gemcutter do
       puts "Processing #{gems.size} gems..."
       gems.each do |path|
         puts "Processing #{path}"
-        cutter = Pusher.new(User.new, File.open(path))
+        cutter = Pusher.new(User.find_by!(email: "[email protected]").api_keys.last, File.open(path))
 
         cutter.process
         puts cutter.message unless cutter.code == 200

Any particular reason to use import task even with advanced seed we have today? I had no need to use import task in last month since I'm happy seed user.

If the import is no longer required, maybe an alternative path would be to remove it as a setup step in CONTRIBUTING.md?