The actual bug mentioned in that PR no longer exists, but it does cause: ~~~~~: error 63 Which this fix cleans up.