As per my previous blog, I did not quite reach GM after Good Bye 2024:
That blog, however, was written before the 2053I2 — Affectionate Arrays (Hard Version) incident:
As a result, to the best of my knowledge, $$$4$$$ participants have been made unrated. While normally this wouldn't be that big of an issue, the $$$4$$$ participants deemed affected by the last problem in the contest were, naturally, quite high up in the rankings.
This, in turn, made me gain $$$2$$$ spots, which, according to Carrot, increased my performance by at least $$$5$$$ points (from either $$$2665$$$ or $$$2667$$$ to $$$2675$$$), which means that I should have reached GM after Good Bye 2024.
For added context, the rating change still shows my rank as $$$157$$$, instead of $$$155$$$:
I am aware that this is incredibly petty (and I probably would have reached GM at some point anyways), but the main reason that I wrote this blog is that the rating changes for Hello 2025 have already been applied, without any sign that the rating chages for Good Bye 2024 will ever be recalculated.
Ig you will see rating changes after rollback that generally codeforces do in time between contest ig not doing because of their maraton challenege that is going on as that that time they will run all the submissions again check for plag and same time increase rating according to new rank
If the Codeforces team were to wait for the end of the MaraTON Challenge, they would have to roll back the rating changes from three rounds (Good Bye 2024, Hello 2025 and the next Div. 2 round), which would be a very funny situation.
With that said, I think that recalculating the ratings while the MaraTON Challenge is running will not really impact the contest (unless there are some technical limitations that I am not aware of).
If Codeforces goes down for an extremely generous $$$3$$$ hours because of this, it would be like losing $$$42.8$$$ seconds from a $$$2$$$ hour round. The main drawback of Codeforces going down for $$$3$$$ hours is that Codeforces goes down for $$$3$$$ hours.
I do have some other theories though:
The ratings have not been recalculated because of a bug. After the $$$4$$$ participants were made unrated, another round of system testing happened, which could have also been intended to recalculate the rating changes. However, since the rating changes had not been reverted beforehand, it didn't do anything.
The Codeforces admins are still waiting for more people that want to removed from the rating recalculation.
They forgor
They wouldn't want to make Codeforces unaccessible for too long. This however is far-fetched since they would have to recalculate the ratings at some point anyway.
Till I found they did not rollback till previous div3 means that contest rating rollback also didn't happen till now so I don't know why they are taking so much time time this time becuase i seen many people they plagged for cheating but in their respective id no changes have been done becuase rollback didn't happen till now ig before before div3 div2 contest rollback also didn't happen i am not sure but till I find out they didn't done it till now it looks like they are going on a winter vacation
pain..
++