Skip to content

core: fix contest ghost export #996

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Conversation

pandadtdyy
Copy link
Member

@pandadtdyy pandadtdyy commented Jun 11, 2025

Summary by CodeRabbit

  • New Features
    • Added 100 extra placeholder teams named "Пополнить команду" to the scoreboard view, each with a unique team ID.
  • Improvements
    • User display names are now shown in the team list if available, with team names displayed in double quotes.
  • Bug Fixes
    • Status code for accepted submissions in the scoreboard view changed from "AC" to "OK".

Copy link

coderabbitai bot commented Jun 11, 2025

Walkthrough

The changes modify the "ghost" scoreboard view in the contest handler. The status code for accepted submissions is updated from "AC" to "OK". The displayed total number of teams is increased by 100 to include phantom teams. When listing teams, the code now prefers the user's display name over their username if available, and team names are wrapped in double quotes. Additionally, 100 placeholder teams named "Пополнить команду" are appended to the team list, each assigned a unique team ID following the actual teams. No exported or public entity declarations were altered.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/hydrooj/src/handler/contest.ts

Oops! Something went wrong! :(

ESLint: 9.28.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@hydrooj/eslint-config' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:201:49)


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c2e4ec3 and 9e937c8.

📒 Files selected for processing (1)
  • packages/hydrooj/src/handler/contest.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/hydrooj/src/handler/contest.ts
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: build
  • GitHub Check: Analyze (javascript)
  • GitHub Check: build
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 80f1158 and 10f76ad.

📒 Files selected for processing (1)
  • packages/hydrooj/src/handler/contest.ts (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: build
  • GitHub Check: Analyze (javascript)
  • GitHub Check: build
🔇 Additional comments (1)
packages/hydrooj/src/handler/contest.ts (1)

788-794: Changing “AC” → “OK” may break downstream importers

Most parsers that consume the “.ghost” format still expect the traditional verdict code AC for an accepted run (cf. PC² / Kattis export specs).
Silently switching to OK risks:

  1. Existing tools suddenly treating all accepted submissions as unknown → scores become zero.
  2. In-house analytics that use string equality on "AC" breaking without compile-time notice.

Please double-check that every downstream consumer understands OK before merging. If in doubt, keep AC or add a compatibility flag.

Comment on lines +817 to 818
Array(100).fill(0).map((_, idx) => `@t ${tdoc.attend + idx + 1},0,1,"Пополнить команду"`),
submissions,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Hard-coded 100 “Пополнить команду” placeholders – fragile & untranslated

  1. The magic number 100 is repeated here and in @teams. Extract it into a constant to avoid divergence.
  2. The Russian label is baked in; non-Russian installations will get unexpected Cyrillic text. Consider passing it through the i18n layer.
  3. The placeholder string isn’t passed through escape, so any future commas/quotes introduced by translation will corrupt the CSV line.
🤖 Prompt for AI Agents
In packages/hydrooj/src/handler/contest.ts around lines 817 to 818, replace the
hard-coded number 100 with a named constant shared with the @teams usage to
avoid divergence. Pass the "Пополнить команду" label through the i18n
translation function to support localization. Also, ensure the translated string
is properly escaped using the existing escape function before inserting it into
the CSV line to prevent corruption from commas or quotes.

Comment on lines +809 to 812
`@teams ${tdoc.attend + 100}`,
`@submissions ${submissions.length}`,
].concat(
tdoc.pids.map((i, idx) => `@p ${pid(idx)},${escape(pdict[i]?.title || 'Unknown Problem')},20,0`),
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Possible team-count mismatch

@teams is now derived from tdoc.attend + 100, while the real list length is teams.length and may differ from tdoc.attend (e.g. spectators, unranked users, withdrawn teams).
If these numbers diverge, many scoreboards will reject the file with “wrong team count”.

Consider:

-`@teams ${tdoc.attend + 100}`
+`@teams ${teams.length + 100}`

or assert that tdoc.attend === teams.length before emitting.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
`@teams ${tdoc.attend + 100}`,
`@submissions ${submissions.length}`,
].concat(
tdoc.pids.map((i, idx) => `@p ${pid(idx)},${escape(pdict[i]?.title || 'Unknown Problem')},20,0`),
`@teams ${teams.length + 100}`,
`@submissions ${submissions.length}`,
].concat(
tdoc.pids.map((i, idx) => `@p ${pid(idx)},${escape(pdict[i]?.title || 'Unknown Problem')},20,0`),
🤖 Prompt for AI Agents
In packages/hydrooj/src/handler/contest.ts around lines 809 to 812, the @teams
count is set using tdoc.attend + 100, which may not match the actual
teams.length due to spectators or withdrawn teams, causing scoreboard
rejections. Fix this by replacing tdoc.attend + 100 with the accurate
teams.length value or add an assertion to ensure tdoc.attend equals teams.length
before emitting the data.

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 this pull request may close these issues.

1 participant