As noted near the end of the article, an Apple employee had already contributed a fix to the bug:

> Checking the latest version revealed the bug was already fixed in v2.4, patched by an ML engineer at Apple last year using almost the exact same approach I’d used.