Skip to content
This repository has been archived by the owner on Dec 14, 2024. It is now read-only.

Wrong test data! #163

Open
3000ye opened this issue Mar 15, 2023 · 7 comments
Open

Wrong test data! #163

3000ye opened this issue Mar 15, 2023 · 7 comments

Comments

@3000ye
Copy link

3000ye commented Mar 15, 2023

As shown in the figure, when I enter the contest with the following command, the downloaded Input data is wrong, which makes it impossible to pass the test no matter what my code is.

cf race 1802

QQ20230315-101423

@vkr2471
Copy link

vkr2471 commented Jul 10, 2023

I have the same issue

@27rabbitlt
Copy link

27rabbitlt commented Jul 18, 2023

have the same issue in Windows 11 with binary release version v1.0.0

@stdout-zhou
Copy link

I think this problem is caused by the upgrade of codeforces.
I have not meet this issue when I start an old contest.
These html content is for selecting a set of test data quickly.

visrut-at-incubyte added a commit to visrut-at-incubyte/cf-tool that referenced this issue Jul 27, 2023
@visrut-at-incubyte
Copy link

Hi folks, can you try to generate a binary from my PR, and see if it's fixed? @vkr2471 @27rabbitlt @stdout-zhou @3000ye

@27rabbitlt
Copy link

27rabbitlt commented Jul 27, 2023 via email

@27rabbitlt
Copy link

27rabbitlt commented Jul 27, 2023 via email

@visrut-at-incubyte
Copy link

I guess the cause is the new html element cf-even-line cf-odd-line. These new attribute is used to display the sample input in different color to distinguishing between different testcase

On Wed, Jul 26, 2023 at 17:37 stdout @.> wrote: I think this problem is caused by the upgrade of codeforces. I have not meet this issue when I start an old contest. These html content is for selecting a set of test data quickly. — Reply to this email directly, view it on GitHub <#163 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A33BDHZGMYPORFW6OPG4643XSDQNBANCNFSM6AAAAAAV3GDOJQ . You are receiving this because you commented.Message ID: @.>

Yes, that was the issue, I changed the parse function to parse that new HTML syntax.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants