My latest submission got judged but the older one is still in queue :p 
My latest submission got judged but the older one is still in queue :p
| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | Benq | 3792 |
| 2 | VivaciousAubergine | 3647 |
| 3 | Kevin114514 | 3611 |
| 4 | jiangly | 3583 |
| 5 | strapple | 3515 |
| 6 | tourist | 3470 |
| 7 | Radewoosh | 3415 |
| 8 | Um_nik | 3376 |
| 9 | maroonrk | 3361 |
| 10 | XVIII | 3345 |
| Страны | Города | Организации | Всё → |
| № | Пользователь | Вклад |
|---|---|---|
| 1 | Qingyu | 164 |
| 2 | adamant | 150 |
| 3 | Um_nik | 146 |
| 4 | Dominater069 | 144 |
| 5 | errorgorn | 141 |
| 6 | cry | 139 |
| 7 | Proof_by_QED | 136 |
| 8 | YuukiS | 135 |
| 9 | chromate00 | 134 |
| 9 | TheScrasse | 134 |
lmao
waiting for dequeforces
In fact, it's a priority_queue :)
UPD: It seems your older submission stucked...It even "In queue" now.
Or maybe just random.
or multisetforces
Actually setforces -- if you attempt to submit the exact same code twice, it'll tell you you already submitted exactly that code before
Ah yeah , you are right
How'd you find out you have the exact same code in your database? Since it is a bunch of text, do you generate a hash and insert in a set?
Yes, its done by comparing hashes. Maybe they store every submissions hash and then compare with every new submission.
Okay
Codeforces didnt like your older submission :P
I think theres more than one workers at play to 'pick' up submissions and then test them, what u face could be due to this, but im not sure.
You might be joking, but on Ukrainian ICPC this year we actually had a submission stack 😭
old but gold
Why does your "My Submissions" list look very old ?
He uses an extension which makes the colors and white theme a bit easier on the eye
interesting