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 | tourist | 4009 |
2 | jiangly | 3773 |
3 | Radewoosh | 3646 |
4 | ecnerwala | 3624 |
5 | jqdai0815 | 3620 |
5 | Benq | 3620 |
7 | orzdevinwang | 3612 |
8 | Geothermal | 3569 |
8 | cnnfls_csy | 3569 |
10 | gyh20 | 3447 |
# | User | Contrib. |
---|---|---|
1 | cry | 161 |
2 | maomao90 | 160 |
3 | awoo | 159 |
4 | atcoder_official | 157 |
5 | -is-this-fft- | 155 |
5 | nor | 155 |
5 | adamant | 155 |
8 | maroonrk | 152 |
8 | Um_nik | 152 |
10 | Dominater069 | 147 |
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