Here is a list of features that we need to implement before launching a testing ICPC contest:

• Show frozen ranking (added in #212)
• Cache ranking (the ranking page will have a lot of traffic)
• Highlight first solved (added in #211)
• TBD

This is a list of issues that should be fixed before release a stable build:

• Could not upload test files larger than 100MB due to the Cloudflare limit. Possible fix: https://github.com/juliomalegria/django-chunked-upload

List of known limitations (not required to fix before the stable build, but nice to be fixed):

• Cannot change problem's code for manually managed problems
• Edit history of problems, blogs, contests, etc., is not shown in the admin panel if edited from UI.
• Edit ticket message.
• The submission score is not updated when we edit the contest problem score.
• Upload test progress bar
• Documenting for #226
• Documenting for VNOI-Admin/judge-server#23

Xây dựng site thành công, khi chấm các ngôn ngữ khác bình thường, tuy nhiên chấm scratch đang bị lỗi:

Một lỗi hệ thống vừa xảy ra trong quá trình chấm bài. Admin VDcoder đã được thông báo về lỗi này.
Bạn có thể thử nộp lại bài trong vài giây nữa

Thông tin về lỗi
Traceback (most recent call last):
File "/judge/dmoj/judge.py", line 406, in _worker_process_main
ipc_msg = next(case_gen)
^^^^^^^^^^^^^^
File "/judge/dmoj/judge.py", line 441, in _grade_cases
self.grader = problem.grader_class(
^^^^^^^^^^^^^^^^^^^^^
File "/judge/dmoj/graders/base.py", line 11, in init
self.binary = self._generate_binary()
^^^^^^^^^^^^^^^^^^^^^^^
File "/judge/dmoj/graders/standard.py", line 104, in _generate_binary
return executors[self.language].Executor(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/judge/dmoj/executors/SCRATCH.py", line 28, in init
super().init(problem_id, source_code, **kwargs)
File "/judge/dmoj/executors/script_executor.py", line 13, in init
self.create_files(problem_id, source_code)
File "/judge/dmoj/executors/SCRATCH.py", line 79, in create_files
source_code = download_source_code(
^^^^^^^^^^^^^^^^^^^^^
File "/judge/dmoj/utils/helper_files.py", line 122, in download_source_code
r = requests.get(link, stream=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/env/lib/python3.11/site-packages/requests/api.py", line 73, in get
return request("get", url, params=params, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/env/lib/python3.11/site-packages/requests/api.py", line 59, in request
return session.request(method=method, url=url, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/env/lib/python3.11/site-packages/requests/sessions.py", line 573, in request
prep = self.prepare_request(req)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/env/lib/python3.11/site-packages/requests/sessions.py", line 484, in prepare_request
p.prepare(
File "/env/lib/python3.11/site-packages/requests/models.py", line 368, in prepare
self.prepare_url(url, params)
File "/env/lib/python3.11/site-packages/requests/models.py", line 439, in prepare_url
raise MissingSchema(
requests.exceptions.MissingSchema: Invalid URL '/submission_file/aplusb/1/09b3bdf0-3eeb-47f7-8d74-83bca68f7be1.json': No scheme supplied. Perhaps you meant https:///submission_file/aplusb/1/09b3bdf0-3eeb-47f7-8d74-83bca68f7be1.json?

Mình nghĩ là phần cài đặt site để chấm scratch đang sai ở đâu đó, rất mong admin chỉ giúp cách sửa lỗi này?

UPDATE: The bug mentioned happens to all buttons on the toolbar. I will still keep the rest of the report to the Image button to act as an example.

Describe the bug

This button does not open a pop-up to paste the image URL as expected.
Note: The button does not work only when replying to another comment (the title underlined being "Replying to comment"). It behaves normally when creating a new comment.

To Reproduce
Steps to reproduce the behavior:

1. Go to any existing comment, and click on the Reply button
2. Click on the Image button

Expected behavior
The following pop-up to allow entering the image URL should appear.

Hi!

I'm one of the authors of DMOJ, love what you've done with VNOJ!

Over the years, you've added many features and fixed many bugs on top of the DMOJ branch, great job on that. Some of them are features we have open tickets for upstream, and some are bugs we also have. (Whoops.)

What are your thoughts on upstreaming some of your changes?

Hopefully, that should also reduce your maintenance burden in the long run, with merge conflicts becoming less likely. We'd of course greatly appreciate this too--most of our effort nowadays goes into the administrative parts of running https://dmoj.ca and making sure the judge chugs along, and less on feature work.

Having skimmed through the changelog, I've listed some changes that stood out to me as "wow I wish we had this upstream" below:

• The (virtual competitor count) display on the contest list
• Contest search; dc4c112
• Option for auto-activating users, this is one of the most frequent support requests we get; 2242a35
• Faster judge problem updates; a860684
• Bugfix for minimum time limit; 17550f3
• Frozen scoreboards

And some that sound relevant, but I wasn't sure applied to upstream:

• Avoid leaking submission feedback when leaving contest; 7beb7f3
• Fix submit button when using back button (what were the symptoms here?); 57a8be1
• Make organization slug unique; a34e284
• Fix IOI contest format; c2cc300
• Fix event server leaking data; 1ce5bb9

As well as anything else you think I missed here.

Let me know what you think, I'm happy to chat more.

This is because the form containing too many problems, which could lead to bad requests. Removing problems fields in the form will fix the problem

Currently, we are not able to send contest notifications to the users. We can create a problem clarification but users need to refresh the problem page to see it.

We can use the notification system of codeforces (show alert to all tab)

In the edit test data, if the problem test data is manually copied to the problem folder, then the UI will not load the data.

Không biết có a nào giúp e được không á

The current About page is a blank page, we need to add more information to that page.
We also need a guide for problem setters.

I suggest these features:
[1] / Top users today
[2] /problems/ Recent 20 unsolved problems
[3] /problems/ Show problem with editorials
[4] /submissions/ Sort by problem
[5] /contests/ Sort on problem (priority: score -> time) (order: rank / asc / dsc)
[6] /contests/Show followers (type: only followers / highlight with full ranking)
[7] /contests/Rating Change
[8] /contests/Highlight First To AC (Priority) <- Highlight Fastest Highest-Score (None-AC)
[9] /contests/Number of users / page
[10] /contests/Freeze Mode (No render update) (type: All / Except Myself)
[11] /contests/Point to me (On page X -> Line Y)
[12] /contests/Highlight myself
[13] /contests/Popup message when changes
[14] /users/ Highlight myself
[15] /contributors/ Highlight myself
[16] /organizations/ Highlight my organizations
[17] /problem/* Except for main-tests from some contests. There should be additional test-cases, hack-tests. And we can select either main-tests or all-tests.
[18] /contests/ Minimalism Mode (Only allow to read popup message, make-read ticket, read clarification, submit-read problem, copy-read my submissions, see total score + total time + remaining time)

========================================

Em suggest feature:
[1] / Top thành viên trong ngày hôm nay
[2] /problems/ Recent 20 unsolved problems
[3] /problems/ Hiển thị bài có lời giải
[4] /submissions/ Lọc theo bài nộp
[5] /contests/ Sort on problem (priority: score -> time) (order: rank / asc / dsc)
[6] /contests/Show followers (type: only followers / highlight with full ranking)
[7] /contests/Rating Change
[8] /contests/Highlight First To AC (Priority) <- Highlight Fastest Highest-Score (None-AC)
[9] /contests/Số người hiển thị / trang
[10] /contests/Chế độ đóng băng (ko render update) (type: tất cả / trừ bản thân)
[11] /contests/ (On page X -> Line Y) [12] /contests/Highlight bản thân [13] /contests/Tin nhắn thông báo khi thay đổi [14] /users/Highlight bản thân [15]/contributors/Highlight bản thân [16]/organizations/Highlight nhóm chứa bản thân [17]/problem/*Ngoài test chính thức, còn có test bổ sung và test hack (có thể chọn chỉ chạy test chính thức hoặc thêm test) [18]/contests/` Minimalism Mode (Chỉ cho thấy thông báo, tạo ticket, đọc ticket, đọc giải thích, nộp bài, đọc đề, copy/đọc bài nộp của bản thân, xem tổng điểm, xem tổng thời gian, thời gian còn lại)

Describe the bug
On the Statistic tab of another user's page, the "Hide problems I've solved" box does not hide problems I have solved.

To Reproduce
Steps to reproduce the behavior:

1. Go to a user's profile
2. Click on "Statistic"
3. Check "Hide problems I've solved"
4. Page gets reloaded, the query string "hide_solved=1" appears but nothing changes otherwise.

Expected behavior
Problems that I have solved should be hidden after the box is checked.

Screenshots

Box unchecked, problem appears

Box checked, problem still appears

Problem solved by user

Desktop:

• OS: Archcraft (5.10.88-2-lts)
• Browser: Brave Browser / Mozilla Firefox
• Version: 96.1.34.53 beta / 95.0.2

Additional context
Tested on both normal and Incognito mode of both browsers.

The icon of unsolved and attempted problems looks like they are forbidden problems

Mô phỏng cách hoạt động của tính năng

• Dựa theo tuần/tháng, tạo ra 3 bảng xếp hạng theo tuần/tháng:
  • Bảng 1 xếp theo số điểm nhận được trong tuần/tháng (tie-break khi số bài nộp AC có chênh lệch, có thể tie)
  • Bảng 2 xếp theo số lần nộp AC (tie-break dựa trên số điểm)
  • Bảng 3 xếp theo rating nhận được trong tuần/tháng (tie-break dựa trên thứ hạng của contest được rate)

Lý do lập tính năng

• Khuyến khích các coder tích cực code để đạt top

"Chương trình tâm lý"

• Có Blog tuyên dương coder theo mỗi kỳ (4 tháng)
• Tổng hợp để đưa vào top ưu tiên trong việc tham gia VNOI-CUP mỗi năm.

We are creating a competitive programing group of PTIT and want to use VNOJ for practicing and we want to track progress of our members in VNOJ. So it would be great if we can choose our university from affiliated organizations list and filter our member in each problem's submission history.

Inside contests, users cannot comment or read other comments.

Currently, only the admin can view the problem link on the contest page if that problem is private. I think this is fine but: When the participants join the contest, it still won't give the problem link, they have to go to "https://oj.vnoi.info/problems/" to view the problem:

• Contest page:
  
• Problem page:
  

I think it would be better if we can show the problem link while the contest is running, and we should not use "https://oj.vnoi.info/problems/" to show to contest problem

The live update is not working as expected. This page can show the submissions that are not in the contest.

We can fix it by get the contest id of the view instead of the request in this line: templates/submission/list.html#L6

Đã đảm bảo việc email đã tồn tại trong một tài khoản của trang

Thông tin hệ thống

• Linux: Ubuntu 22.04 TLS
• Chạy website bằng Docker image (đã có chỉnh sửa /repo lên bản mới nhất)

On 500 error, the site will throw a blue screen to user and it really scary (who want to see the blue screen?): https://github.com/VNOI-Admin/OJ/blob/master/templates/error.html

On 502 error, the site will display the name of DMOJ. https://github.com/VNOI-Admin/OJ/blob/master/502.html

If you search with the full-text search option, an error will occur because the default database not support full text search. You have to do it by hand:

ALTER TABLE judge_problem ADD FULLTEXT(code, name, description);

Or you can set Enable_FTS to False in the local_settings
Source: DMOJ/docs#100

Lots of online judges have a code window under the problem statement of a problem, whereas our UI have a comment window instead. People would just simple copy+paste their code into the comment window without noticing the window is for commenting.

Some languages cough scratch cough is not submittable via text (actually yes but not user friendly). We need to allow users to submit via file.

However, the current database schema is not able to do it, and I think we should not mess with it.

Here is a solution:

Site server:

• Create a new field in the Problem model (for example: allow_file_submit).
• With problems that allow submitting via file, we allow users to upload a file into a folder. We create an URL to download that file
• Send that URL to judge the server

Judge server:

• Download the submission file by that URL, and then continue to judging.

Seem like the live update is not updating submission in a contest.

Like title.

https://oj.vnoi.info/contest/<contest_name>/submissions/<user_name>/<problem_name>

To support the Official Contests, we need to add a new mode: Official Contest Ongoing

In this mode:

• Must have:
  • No one can view any submissions, even their own submissions.
  • To prevent solution spoilers, no one can add new comments.
  • To prevent spam that can overload the judge server, except the contestants, no one can submit submissions.
• Optional:
  • Disable viewing old blogs, comments, editorial of old problems.

Currently, the site is caching all flat pages in 1 day. There should be a feature to clear the cache of the flat page automatically after we edited it.

This is because the suggester doesn't have permission to upload directly to the server.

If we change problem points in admin UI, everything is fine, all submissions of that problem will change points.

Thing will go wrong if we update problem points via shell/ the current form.

Describe
The Contest's Score updater run too slow to update the Contest's results when I change the Contest's Format

This is due to a missing </b> tag when doing l10n.

https://github.com/VNOI-Admin/OJ/blob/master/locale/vi/LC_MESSAGES/django.po#L4242

Currently, the filter by status is actually using Submission Result instead of Submission status.

However, we might want to filter submission status (like Queuing, grading, ...)

This markdown:

```
~
```

```
~
```

Expected:

Result:

This is because the way we capture math expression

I had installed VNOJ using docker-compose using instructions from https://github.com/VNOI-Admin/vnoj-docker and having this problem. I'm assuming that I'm having some problem with wsevent but I couldn't find out how to fix it. I found this issue DMOJ/online-judge#924 but after trying all node versions from 12 to 19, it still didn't work. Thanks for any help.

Currently, we have a rule about the comment here.

I think we should add the comment rule in the comment section

If a user clicks to the "my submission" in a contest that they haven't participated in, the site will throw an 404 error.

This because of this line views/submission.py#L640 and this views/submission.py#L610

I have 2 solutions for this issue, but it depend on n what we want to do:

1. Don't show the "my submission" tab if the user hasn't joined the contest
2. Just remove the 2 lines above -> this way, if the user hasn't joined the contest, the submission page will be empty (don't have any submission)

When a submission receives partial points for a test case, the verdict is showing as AC. That could make users think that they got AC if they are not carefully read the points.

Perhaps we should change the color of the verdict?

By the way, the submission verdict always shows as the short name (AC instead of Accepted). I think we should show the full name here?

Describe the bug
Users can view Submission List of others in contest time even if the show_submission_list is set to false.

To Reproduce
Steps to reproduce the behavior:

1. Create a private problem A
2. Create a contest containing A (set show_submission_list to false)
3. User join that contest
4. User cannot see others submissions in /contest/<contest_id>/submissions/ but they still can see others submission in problem/A/submissions/

Expected
User cannot see others submissions in /contest/<contest_id>/submissions/ and problem/A/submissions/

There are many problem statements that we haven't had the markdown version of yet (example: https://oj.vnoi.info/problem/bustour)

We should have the ability to embed the PDF statement in the problem statement.

Add any other context about the problem here.
File "/usr/local/lib/python3.11/site-packages/django/db/models/fields/related_descriptors.py", line 197, in get
raise self.RelatedObjectDoesNotExist(
judge.models.profile.Profile.user.RelatedObjectDoesNotExist: Profile has no user.

The site adds 2 # automatically if # is at the beginning of a line to offset the heading.

But it should not add # if the # is in a block code:

This happened because of this: 08575ab

Before the contest UI rework (#24), problem clarifications would show on the homepage. Now they don't show up and we should move it to the contest page as well.

Hi all,

I'm following the setup instruction of DMOJ to setup on source VNOJ but when I ran command 'pip3 install -r requirements.txt', I got an error in the following image:

I'm not good at Python so I don't know this error is a bug or my setup was wrong in any step. Please help me!