Please read the new rule regarding the restriction on the use of AI tools. ×

hossameldeenfci's blog

By hossameldeenfci, 11 years ago, In English

Whenever I open any problem, whether from the problemset or contests page, whether on English or Russian version of the website, the website reopens the last page I opened, and a popup message says "Can't read or parse problem descriptor".

I've already known several people are having the same issue (don't know anyone not having it currently)

So, is there any announcement on this problem somewhere? And when is it expected to be fixed?

UPD: Problem is now solved, I think. I can open problems again :)

  • Vote: I like it
  • +9
  • Vote: I do not like it

| Write comment?
»
7 years ago, # |
  Vote: I like it -6 Vote: I do not like it

wow four years ago..

I have same problem with http://codeforces.net/gym/100298/problem/A now..

»
13 months ago, # |
Rev. 2   Vote: I like it +24 Vote: I do not like it
Spoiler
  • »
    »
    13 months ago, # ^ |
      Vote: I like it +6 Vote: I do not like it

    Man.. I just started last div3 contest in virtual mode, did A, then going to open Problem B...And BOOOOOM..

    • »
      »
      »
      13 months ago, # ^ |
      Rev. 2   Vote: I like it +13 Vote: I do not like it
      >start virtual
      >WA test 2 on div. 2 B
      >WA test 2 on div. 2 C
      

      haha oopsies, i guess the virtual is messed up because of codeforces! guess this one doesn't count! oh well, nothing i can do about that!

  • »
    »
    13 months ago, # ^ |
      Vote: I like it +3 Vote: I do not like it

    Can't read or parse problem descriptor

    sadge, I guess we can probably use vjudge in the meantime.

    example: https://vjudge.net/problem/CodeForces-1692A

»
13 months ago, # |
  Vote: I like it +5 Vote: I do not like it

saame

»
13 months ago, # |
  Vote: I like it +5 Vote: I do not like it

Lol this problem occurred 10 years ago too

»
13 months ago, # |
  Vote: I like it 0 Vote: I do not like it

Screenshot 2023-09-12 181736.png

»
13 months ago, # |
Rev. 2   Vote: I like it 0 Vote: I do not like it

It seems to be fixed now