The documentation of update_manager_archive_extract() in update.manager.inc implies that it should take project name $project as an argument, but it doesn't in the current implementation.
See #538660: Move update manager upgrade process into new authorize.php file (and make it actually work) and #1019834: No .info files reported on theme upload when zip created with certain programs for the original documentation history and project name auto-discovery, respectively.
We ran into this because of a malformed tarball where the project name wasn't easily deduced from the archive contents. The function is called by another module (the openpublish install profile).
In most circumstances when invoking this function in code (as is the case with openpublish) you generally have the $project already defined, so there isn't a need to automatically determine the name.
In cases like #1019834: No .info files reported on theme upload when zip created with certain programs where someone uploads a project to be installed, there may be a need for the automated stuff.
Comments
Comment #1
dooug commentedComment #1.0
dooug commentedfix project node links
Comment #4
quietone commentedUpdating tags per Issue tags field and Issue tags -- special tags and for issue #3565085: Drupal core issue tag cleanup.