Yea something's been stuck with that on this instance of Allura. I haven't seen it happen on any other Allura instances, so we'll have to look into the data & tasks here to see what's going on.
The activitystream library prevents concurrent updates, but if an update failed then the flag was never reset, and activity updates would never run for that node again. Fixed with mongo cmd:
Yea something's been stuck with that on this instance of Allura. I haven't seen it happen on any other Allura instances, so we'll have to look into the data & tasks here to see what's going on.
The project still does have activity, check out the git commits or mailing list etc.
The activitystream library prevents concurrent updates, but if an update failed then the flag was never reset, and activity updates would never run for that node again. Fixed with mongo cmd:
db.nodes.update({is_aggregating:true}, {$set: {is_aggregating:false}}, {multi:true})