The code is still in-tree but the feature is disabled at the moment, and it seems stable like that. We need to address the issues in that incident report to determine what caused the problem and how to test for it on qastaging before this goes live again.
This was deployed last week, but it seemed to start spinning and it had to be shut down.
https:/ /wiki.canonical .com/IncidentRe ports/2011- 02-11-Codehosti ng-Forking- Service- Down
The code is still in-tree but the feature is disabled at the moment, and it seems stable like that. We need to address the issues in that incident report to determine what caused the problem and how to test for it on qastaging before this goes live again.