Initial run of this module's report (where presumably the original releases are downloaded) takes too long and PHP times out. Does this module attempt to extend the PHP timeout at runtime? Is it coded so that instead of downloading packages that it just downloaded it resumes with ones that it hasn't yet downloaded? Watching the /tmp directory while it runs makes me think not.
If this takes too long to run and doesn't have a provision for running via multiple attempts... how do I use it?
Thanks!
Comments
Comment #1
msielskiSorry, wasn't a timeout but was out of memory. I got it running eventually. Batch API would be great for this project.
Comment #2
steven jones commentedIndeed it would.
Duplicate of #811366: batch API integration