Update module (still) creates duplicate queue items

This looks like the same issue as #952394: "No available releases found" - fetching update information exceeds timeout, marking duplicate.

Yes I'm pretty sure it's the same issue or closely enough related that we don't need to track it in two separate issues.

It'll be fixed when someone writes a patch for it, then that patch is reviewed and committed, same as any other bug.

I would like to reopen this because I believe it is different from the issue it was declared of duplicate of.
I read the whole thread and the other issue seems to be focusing on the auto check that happens when reaching admin/reports/updates not on manual checking that loops and never ends. I also commented this here https://drupal.org/node/952394#comment-8778231
So I am facing this too, manual checking of available updates takes 10 times more than it should, this is very annoying.

It took more than 5 full minutes and tells me it checked the update of 773 modules where I only have 80 to 100 modules enabled.

If I manually check again right after that, it takes a decent time (20 to 30 seconds) and tells me it checked for 79 projects.

This actually stills works after I clear the cache. But I know in a few days it will go back to 5 minutes...

We should use the batch API for this. It'll still take a long time, but it'll show progress etc.

Ok I trust you with the Batch API thing but I believe title should keep describing the problem people are facing not the next step in what could solve it.
That way people can more easily find already open issue to join instead of creating duplicate. Also when reading the list of fixed issues on the Drupal core release it's easier to understand what's been fixed.

Now back to the Batch API, I'm a bit skeptical about what you say this will do... you say it won't fix the fact that it is slow but we will now see progress... well I already see the progress bar progressing correctly. It actually is progressing correctly right from the start so I immediately know if it's gonna last 30 seconds or 5 minutes.

This might actually be a clue in solving this issue! The problem seems to be in the initializing phase, not when checking updates via http. Looks like when I haven't manually checked updates for a long time, initializing phase will conclude that there are 773 projects to check instead of 79 projects.

Is your 7.x install up to date?

I vaguely remember that bug, but I think it was either fixed, or there's a patch to be backported somewhere.

Almost yes. 7.27 so unless it's been fixed in 7.28 I guess it hasn't been fixed yet. But I'm a bit reticent to upgrade to 7.28 now that I read this https://drupal.org/node/952394#comment-8749635 I rather wait for a final patch before upgrading to 7.28

OK so that issue was #1492188: Update module creates duplicate queue items. If there's still duplicate queue items it's possible that hasn't fully fixed the issue.

indeed

Does the problem still exist, or should we close this as "probably fixed"?

Let's close as cannot reproduce, haven't seen this mentioned anywhere since the last time I posted on here.