CC-1731: Fix Redis #bs1 and #xu1

[andy1li]

Summary by CodeRabbit

• Bug Fixes
  • Corrected the expected response structure for stream entries in the "Blocking reads" stages to match the updated format.
  • Updated blocking timeout durations in descriptive text and examples from 2000ms to 1000ms for improved accuracy.

[linear]

CC-1731 Fix Redis #bs1 and #xu1

[coderabbitai]

Walkthrough

The update modifies the YAML course definition for a Redis challenge, specifically focusing on the "Blocking reads" stages involving the XREAD command with the BLOCK option. The changes adjust the expected RESP array structure for stream entries by introducing an additional nesting level around the entry ID. Additionally, the blocking timeout durations in the descriptive text and example commands are reduced from 2000 milliseconds to 1000 milliseconds in three instances. No changes were made to exported or public entity declarations.

Changes

File(s)	Change Summary
course-definition.yml	Updated expected RESP array structure for stream entries by adding a nesting level around entry IDs; reduced blocking timeout durations in text and examples from 2000ms to 1000ms in relevant "Blocking reads" stages.

Poem

🐇
A hop and a skip, the streams rearrange,
IDs now nested, a structural change.
Time ticks a bit faster, a thousand will do,
For blocking reads waiting for something new.
In the warren of YAML, the challenge refined—
Redis commands and rabbits, perfectly aligned!

---

📜 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 f584fec and c371508.

📒 Files selected for processing (1)

• course-definition.yml (3 hunks)

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

• GitHub Check: test_course_definition / test (swift)
• GitHub Check: test_course_definition / test (scala)
• GitHub Check: test_course_definition / test (ocaml)
• GitHub Check: test_course_definition / test (kotlin)
• GitHub Check: test_course_definition / test (haskell)

🔇 Additional comments (4)

course-definition.yml (4)

2897-2901: Approve nested RESP array structure for blocking XREAD.

The example response now correctly represents each stream entry as a two-element array [<ID>, [<field>, <value>, …]] instead of a flat list. This aligns with Redis’s RESP format for nested arrays.

---

3153-3157: Approve nested RESP array structure for $-based blocking XREAD.

The updated example for the $-blocking XREAD now wraps each entry ID and its fields/values in an inner array, matching the RESP spec. Great catch!

---

3165-3165: Verify updated blocking timeout for $-based XREAD.

The description now references a 1000 ms wait for the $-based blocking read. Confirm consistency across all XREAD BLOCK examples.

---

2908-2908:

✅ Verification successful

Confirm timeout consistency in XREAD descriptions.

The blocking timeout has been reduced to 1000 ms. Ensure no remaining references to the old 2000 ms timeout in this YAML file.

Run:

---

🏁 Script executed:

grep -R "2000" course-definition.yml || echo "No 2000ms references found"

Length of output: 99

---

Timeout consistency verified and up to date

I’ve searched the entire course-definition.yml and confirmed there are no remaining 2000 ms references—only the updated 1000 ms timeout remains. No further changes needed.

---

🪧 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 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.