So it turns out the implementation in in patch 2729 still errored out mahara.org. By placing a lot of log_info() statements throughout the activity_process_queue() cron job, I was able to trace the crash to the part where it does activity_get_users().
The reason this is a problem, is because patch 2729 doesn't actually chunk the data pulled from the database; instead, it pulls the full amount of data and then only processes a subset of it. So, I've submitted a patch which actual alters ActivityInteractionForumNewPost so that only pulls CHUNK_SIZE users from the DB each time. With this patch, the mahara.org News forum actually sends out notifications! https://reviews.mahara.org/2790 -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/778254 Title: Split multiple user activity notifications into chunks Status in Mahara ePortfolio: In Progress Bug description: See bug #716812. When there are lots of users that need to be notified about a single activity, they need to be chunked and processed over several cron runs to avoid running out of memory. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/778254/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
