Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Samples couldn't be crawled when the "sample" label is non-English in Vjudge #446

Closed
Yerosius opened this issue Apr 11, 2024 · 4 comments
Closed

Comments

@Yerosius
Copy link

Yerosius commented Apr 11, 2024

In Vjudge, when the "Sample" label is non-English, it will lead to failure to crawl samples.

The situation will be caused when the statement is non-English or using Vjudge's GPT translation into a non-English language.

@Yerosius Yerosius changed the title Sample can't be crawled when the "sample" label is not in English in Vjudge Sample can't be crawled when the "sample" label is non-English in Vjudge Apr 11, 2024
@Yerosius
Copy link
Author

By the way,when the statement is provided in document form(such as UVA OJ),the samples can't be crawled,too.

@Yerosius Yerosius changed the title Sample can't be crawled when the "sample" label is non-English in Vjudge Samples couldn't be crawled when the "sample" label is non-English in Vjudge Apr 11, 2024
@touhidurrr
Copy link
Contributor

touhidurrr commented May 25, 2024

Hi, @Yerosius. Can you provide some problem links so that I can test this?

@Yerosius
Copy link
Author

Yerosius commented May 25, 2024 via email

touhidurrr added a commit to touhidurrr/competitive-companion that referenced this issue May 25, 2024
@touhidurrr touhidurrr mentioned this issue May 25, 2024
@jmerle
Copy link
Owner

jmerle commented May 26, 2024

I've fixed the parsing of sample cases on Chinese problems like the one you linked in d592027, and added support for parsing sample cases on UVA and UVALive problems in 3b4ed00. The latter only works in Chrome for now due to a bug in Firefox (https://bugzilla.mozilla.org/show_bug.cgi?id=1757836), it's prioritized as P2 which means that it should be fixed in Firefox's next release cycle or the following.

These changes will be released within an hour. Thanks for reporting the issues!

@jmerle jmerle closed this as completed May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants