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 | Benq | 3676 |
| 2 | Kevin114514 | 3659 |
| 3 | jiangly | 3640 |
| 4 | turmax | 3450 |
| 5 | tourist | 3382 |
| 6 | strapple | 3360 |
| 7 | Um_nik | 3354 |
| 8 | squareOf105 | 3348 |
| 9 | maroonrk | 3312 |
| 10 | idontwannadothis…e | 3191 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 155 |
| 2 | nik_exists | 151 |
| 3 | maspy | 149 |
| 4 | AmShZ | 145 |
| 5 | Um_nik | 143 |
| 6 | Errichto | 139 |
| 7 | BledDest | 136 |
| 8 | adamant | 134 |
| 9 | maroonrk | 132 |
| 10 | cry | 130 |
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