No problem, it would just be nice to keep such situations to a minimum.

seems like google ddosed you for kickstart XD

Thank you for addressing this problem & investigating the reason behind it.

It's ok.We haven't forgotten the 99% time it hasn't gone unrated

Its fine ^_^, it might be a kind of bug that you cant find until you get a WA once.

The moment i solved A quickly.. Unrated contest : Hold my beer ! :(

Can we please try to avoid making the Div1 round unrated when such things happen? Since the load is small, that should be doable by sacrificing Div2.

Thanks for the work though Mike :)

Noooooooooooooooooooooooooooooo

Thanks for your efforts, Mike.

The "In Queue" problem was present much before the contest. I tried practicing 2 problems around 5:OO PM IST. Submission of both these problems resulted "In Queue". The contest started at 8:05 PM IST.

Thank you.

That's not a big problem , thx for ur efforts

no problem dude.. thanks for letting us know the fact

thanhchauns2 the odds are against you

Call hecker

is there any chance that rating changes can be distributed to the participants or is that out of the question?

No issues, the community is grateful to you and respect the efforts that you put into every contest :)

What's up

i successfully fu*ked up with contest. i was solving problems in problems set and made lot of submissions and finally i shaken up whole codeforces.

Did anybody get "Unexpected error" when you submit? I got it when tried to submit A.

Recently someone try to drop some bug in blog post, Is there any chance that he/she or them can create a bug for slow down judging system?

These contests (the ones with slow judging time or Codeforces being down) are the best ones for me to prepare for our IOI selection contest. LOL

thanhchauns2 Are you ready ?

i just did some stupid things in this contest.Fortunately, it's unrated.

DDOS by google. XD

no problems!

So, these problems will be unrated. won't they?

A similar issue happened in the CCPC contest (China Collegiate Programming Contest) in August 28. Maybe all we need is a powerful server.

can anyone tell my any idea how to solve problem E div2 it was tagged as dp but I am not to find any recursive relation

I like the solution where only people with positive delta get rated. (:

You should have extended the time of the competition, that way no one would be upset, neither the authors,nor the contestants and nor you.

Edit: Why downvoting me guys? Did I say something wrongly??

Problems were great anyway, thanks

Майк: пацаны, у меня серваки упали, не знаю почему, никогда такого не было и вот опять, пытаюсь понять, что в этот раз отвалилось

Сообщество: +764

Because of the accident, I think we should give thanhchauns2 an extra chance to avoid his head becomes completely bald :))

In fact, the page was stucked in the first 1min in most of the rounds……

but this round was stucked too long, just like the cf round which was attacked by ddos in the past

A huge thank you for the unvaluable work you have been doing since more than a decade for the coders community. Please no reason at all to be upset. It is surely something sneaky that will be caught soon. If it can help, during the contest I had B passed while A was still in queue.

@Mike what was the RCA

Ok, that's fine to me, I spent 20 minutes on A

Sorry for my good ranking,but that is all right.

There's no reason to be upset. After all, Codeforces itself is a great website. I am also very grateful to Codeforces for greatly improving my programming level.

Also, this doesn't happen often. Most of the contest have brought me a good experience. To be honest, it is not easy to ensure the normal operation of the website when the number of participants reaches 10k+ and even 20k+, and Codeforces has done it, which shows that Codeforces is a great website. This is also why codeforces has not only been loved by domestic people since its establishment, but also widely recognized by programmers in many other countries.

Of course, I can understand the mood of management in case of emergency. But I think there's no need to be so upset. Since Codeforces has gone through 12 years, it has shown that this website is very good. And I believe that Codeforces will be better in the future! :)

and I lose my 10 days in the row

Кто-то просто выложил списки УГ на кодфорцес...

Comment is hidden because of too much negative feedback, UPVOTE to make it visible again.

To know the reason , watch this

Am I right that everything worked well today? That there weren't any issues with the website or testing speed?

After the round ended, I re-tested this Div. 2 and one of the old rounds, along the way profiling my code.

Some database queries took an unusually long time. I optimized some of these queries, making them much faster.

Note that this behavior has not been observed before — I have profiled this code repeatedly under load before. It seems that the issue is more in the database state, the performance of the DB for some reason has degraded. At the same time, metrics from the database itself did not show anything unusual.

The reboot of the DB helped by speeding up the testing by ~10 times. At the same time, the DB itself stopped for an unusually long time during the shutdown (this could happen with MariaDB if it has issues with its current state).

I updated MariaDB to the latest minor version (I had to read all the changelogs and update the server along the way). Configured monitoring and alert in case queries to some tables start to work for an unusually long time. Broke and repaired slave for live backup. Fixed night backups (oh yes, they broke mariabackup in one of the versions). I re-tested the rounds a few more times to make sure the fast work is reproducible.

Something else worked longer than expected due to overgrown tables that held some meta-information on submissions and custom invocations. All this information is not needed for long-term storage. I have configured nightly deletion of data older than a few days from such tables.

As a result, I was pretty confident that today's round should have gone well in terms of testing speed. And so it happened. Hooray.

There is queue again.
UPD: not anymore.