If anyone runs into this same problem today, sorry, we merged a gem update that seems to have caused the same problem
We think it’s broken as of:
and fixed as of: