A Rake task for updating gems' download counts

[janko]

I noticed that you don't have a task for that. I also noticed that rubygem records are updated very rarely with their number of downloads. Hopefully, now that you have this task, you can put it as a scheduled task to be run regularly (at least once a month, if it's possible).

I'm aware how big the rubygems table is, so I was careful about the memory. I've also written the task in a way that only 1 SQL query is executed for updating all rubygems.

[janko]

Please, take a look at the issue #432 for why this is important.

[travisbot]

This pull request passes (merged 0903014c into 29fabb2).

[travisbot]

This pull request fails (merged 1d02d195 into 29fabb2).

[cmeiklejohn]

It looks like your latest changes broke the test suite -- can you investigate why?

[janko]

Well, I don't know why they broke – all I did was add a rake task. Maybe the tests were failing on master at the moment when I updated my commit.

But that reminded me that I should really write tests for this rake task. I will report here when I've written them.

[cmeiklejohn]

Sweet, thank you.

[cmeiklejohn]

Looks like your failure is related to #438 and not your change.

[adkron]

@janko-m Are you still working on this?

[janko]

Yes, I'm sorry for taking so long, I intend to finish this.

[janko]

I added the tests :)

I'm wondering, do you get a notification when I amend a commit (like I did here)? Because I always put a comment after I amend just in case, and I'd rather not if you do get a notification :P

[sferik]

FYI, I only receive notifications of comments, not of pushes. Thanks for working on this (and following-up).

[janko]

My pleasure :)