Yes, it is. But clearly in a different codebase. Crazy that two teams were using this same esoteric, broken prctl and diagnosing the problem it caused in such short succession.
Haha, yea. When I was writing this blog post (we had already pushed to production) I came across that post when searching for sources to confirm my findings. Antonio and I were so surprised at the coincidence.