| # | User | Rating |
|---|---|---|
| 1 | Benq | 3676 |
| 2 | jiangly | 3670 |
| 3 | Kevin114514 | 3657 |
| 4 | maroonrk | 3355 |
| 5 | Um_nik | 3353 |
| 6 | squareOf105 | 3346 |
| 7 | tourist | 3343 |
| 8 | strapple | 3324 |
| 9 | heuristica | 3322 |
| 10 | jiangbowen | 3291 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 158 |
| 2 | nik_exists | 150 |
| 2 | maspy | 150 |
| 4 | AmShZ | 143 |
| 5 | Um_nik | 141 |
| 6 | Errichto | 139 |
| 7 | adamant | 137 |
| 8 | BledDest | 133 |
| 8 | maroonrk | 133 |
| 10 | qwexd | 130 |
|
+8
I think many share the same trouble during the contest so I don't want to make this only about myself. |
|
+19
Please make the round unrated for those who got "Idleness limit exceeded" in Problem C because of sending too many requests. It was explicitly stated in the statement that sending too many requests leads to "Wrong Answer" and printing nothing or forgetting to flush the output leads to "Idleness limit exceeded". It wasn't until almost the end of the contest that the correction was made. Some contestants may have spent huge amount of time looking for errors in their code that matched the verdict("Idleness limit exceeded")and couldn't find any mistake related to I/O and therefore couldn't compete in the contest normally. Please look into the issue. |
