I didn't detect this because I had the old workaround in place, but after #178, I suppose that 640468165c05611ba81d76b757fd3f195a93b285 broke this?