Hello.
If you are not sleeping now, join to Testing Round 8. Thanks!
Thank you for participation. See you tomorrow on MemSQL start[c]up Round 1.
# | User | Rating |
---|---|---|
1 | jiangly | 3898 |
2 | tourist | 3840 |
3 | orzdevinwang | 3706 |
4 | ksun48 | 3691 |
5 | jqdai0815 | 3682 |
6 | ecnerwala | 3525 |
7 | gamegame | 3477 |
8 | Benq | 3468 |
9 | Ormlis | 3381 |
10 | maroonrk | 3379 |
# | User | Contrib. |
---|---|---|
1 | cry | 168 |
2 | -is-this-fft- | 165 |
3 | Dominater069 | 161 |
4 | Um_nik | 160 |
5 | atcoder_official | 159 |
6 | djm03178 | 157 |
7 | adamant | 153 |
8 | luogu_official | 151 |
9 | awoo | 149 |
10 | TheScrasse | 146 |
Hello.
If you are not sleeping now, join to Testing Round 8. Thanks!
Thank you for participation. See you tomorrow on MemSQL start[c]up Round 1.
Name |
---|
Joined but it would be nice to get a bit more info. Share with us new changes which are being tested)
All of them are very internal. The main reason of testing round is that I don't want to have any untested changes before MemSQL start[c]up Round 1.
Also I tested transparent traffic switching between two Codeforces instances. It makes possible to restart/update/redeploy the system without downtime.
Regarding the 2nd part — I would say the feature is not as internal as you say — this is very important to us) Having a broken system during the contest is very annoying. Thanks
Problem A:
Oops