It seems that Judge Protocol work in ongoing contest. It this a bug ? 
→ Обратите внимание
→ Лидеры (рейтинг)
| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | Benq | 3857 |
| 2 | jiangly | 3810 |
| 3 | maroonrk | 3534 |
| 4 | tourist | 3528 |
| 5 | Kevin114514 | 3510 |
| 6 | turmax | 3411 |
| 7 | Um_nik | 3387 |
| 8 | Radewoosh | 3367 |
| 9 | heuristica | 3322 |
| 10 | strapple | 3317 |
| Страны | Города | Организации | Всё → |
→ Лидеры (вклад)
| № | Пользователь | Вклад |
|---|---|---|
| 1 | Qingyu | 158 |
| 2 | maspy | 150 |
| 3 | Um_nik | 146 |
| 4 | Errichto | 139 |
| 5 | adamant | 136 |
| 6 | maroonrk | 134 |
| 7 | DNR | 133 |
| 8 | Dominater069 | 131 |
| 8 | nik_exists | 131 |
| 10 | Proof_by_QED | 130 |
→ Найти пользователя
→ Прямой эфир
Codeforces (c) Copyright 2010-2026 Михаил Мирзаянов
Соревнования по программированию 2.0
Время на сервере: 03.09.2026 17:59:11 (g2).
Десктопная версия, переключиться на мобильную.
При поддержке
This is a serious bug.
Source?
I mean in the general sense. Imagine code failing due to overflow and then checking judge protocol and finding that out. There is no way this was intended.
Then you should have indicated that it is a guess and not a known fact.
To me nothing is obvious.
Someone who is not familiar with Codeforces might not think there is anything strange about that. It may look like a bug to someone who is not used to that kind of feedback, but in itself there is nothing so obviously wrong with it that you can just know that it is not intended without proving it.