a small patch that fixed that issue was pushed a few minutes after the change was pushed, just needed to reload from the web server