[HTTP] Add notes related to anti-cheat tests

[andy1li]

Summary by CodeRabbit

• Documentation
  • Updated course instructions to clearly specify that the HTTP server must be implemented from scratch using low-level TCP operations, disallowing the use of built-in HTTP libraries.
  • Added notes to enhance understanding of implementation requirements and provided references to external documentation on HTTP responses.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates the course-definition.yml file by modifying the description of the HTTP server challenge and adding notes regarding implementation requirements. The description now specifies that participants will build an HTTP server "from scratch using TCP primitives," clarifying expectations for server capabilities. Two new notes sections emphasize the use of TCP primitives and provide a reference to external documentation on HTTP responses, enhancing clarity without altering existing functionality.

Changes

File	Change Summary
course-definition.yml	Modified the description to specify building the HTTP server from scratch using TCP primitives; added notes on implementation requirements and external documentation.

Poem

Hop, hop, I write with glee,
A rabbit coding wild and free.
TCP tricks in each new line,
No built-in magic—pure design.
Course notes clear, a guiding art,
With each hop, we finish smart!
🐇✨ Enjoy the build!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 5d2b780 and d001260.

📒 Files selected for processing (1)

• course-definition.yml (4 hunks)

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

course-definition.yml (1)

44-45: Clear Global Requirement Note:
The newly added note at line 44 effectively emphasizes that participants must implement the HTTP server from scratch using TCP primitives and must not use built-in HTTP libraries—a key anti-cheat measure.

Consider unifying note styles by, for example, prefixing this global note with a markdown header (e.g., ### Important:) to match the formatting used elsewhere in the document.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8c0d3d8 and 5d2b780.

📒 Files selected for processing (1)

• course-definition.yml (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: test_course_definition / test (kotlin)
• GitHub Check: test_course_definition / test (haskell)
• GitHub Check: test_course_definition / test (cpp)

🔇 Additional comments (1)

course-definition.yml (1)

191-193: Stage-Specific Reminder Consistency:
The note added at line 191 reinforces the global requirement in the context of the "Bind to a port" stage, reminding participants not to use built-in HTTP libraries. This redundancy helps ensure that the requirement is front and center at a critical point in the course workflow.

Optionally, you may consider if the similar reminders across the global description and this stage could be consolidated to reduce repetition, or if the current approach better underscores the importance of the rule.