Skip to content

Conversation

leynos
Copy link
Owner

@leynos leynos commented Jul 4, 2025

Summary

  • add test to cover time-based queue fairness when max_high_before_low is zero

Testing

  • make fmt
  • make lint
  • make test
  • cargo test fairness_yields_low_with_time_slice -- --nocapture

https://chatgpt.com/codex/tasks/task_e_68684cd037548322a494feb0d1e8476d

Summary by Sourcery

Tests:

  • Add fairness_yields_low_with_time_slice test to ensure low-priority items are yielded in the middle of the stream based on the time_slice setting.

Copy link
Contributor

sourcery-ai bot commented Jul 4, 2025

Reviewer's Guide

Adds a new integration test that configures ConnectionActor with a zero high-before-low limit and a 10 ms time slice, then drives the actor through interleaved high- and low-priority pushes to verify low-priority items are emitted in the middle of the sequence once the time slice elapses.

File-Level Changes

Change Details Files
Add time-slice fairness test for ConnectionActor
  • Imported Duration, tokio::sync::oneshot channel, and tokio::time::sleep
  • Configured FairnessConfig with max_high_before_low=0 and time_slice=10ms
  • Spawned the actor run loop and captured its output via oneshot
  • Interleaved pushes of high- and low-priority items with timed sleeps
  • Asserted that the low-priority item appears mid-sequence
tests/connection_actor.rs

Possibly linked issues

  • #0: PR adds the requested test for time-based fairness with max_high_before_low zero, directly addressing the issue.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Contributor

coderabbitai bot commented Jul 4, 2025

Summary by CodeRabbit

  • Tests
    • Added a new test to verify that low-priority items are correctly yielded when using time slice fairness settings.
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in a Comment
  • Commit Unit Tests in branch codex/add-test-for-fairness-with-time_slice-yielding

🪧 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 auto-generate unit tests to generate unit tests for 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
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @leynos - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@leynos
Copy link
Owner Author

leynos commented Jul 4, 2025

@coderabbitai review

Copy link
Contributor

coderabbitai bot commented Jul 4, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@leynos
Copy link
Owner Author

leynos commented Jul 4, 2025

@coderabbitai review

Copy link
Contributor

coderabbitai bot commented Jul 4, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@leynos
Copy link
Owner Author

leynos commented Jul 5, 2025

@coderabbitai review

Copy link
Contributor

coderabbitai bot commented Jul 5, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link
Contributor

@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: 1

🔭 Outside diff range comments (2)
tests/connection_actor.rs (2)

17-17: Replace forbidden #[allow] attributes with #[expect].

The coding guidelines explicitly forbid #[allow] and require narrowly scoped #[expect(lint, reason = "...")] instead.

-#[allow(unused_braces)]
+#[expect(unused_braces, reason = "rstest fixture requires braces for consistency")]

Apply this change to all three fixture functions.

Also applies to: 21-21, 25-25


117-146: Add missing test attributes to prevent clippy error.

The function fairness_disabled_processes_all_high_first is missing the #[rstest] and #[tokio::test] attributes, causing it to be unused and triggering a clippy error.

+#[rstest]
+#[tokio::test]
 async fn fairness_disabled_processes_all_high_first(
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fe4508f and 6692601.

📒 Files selected for processing (1)
  • tests/connection_actor.rs (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.rs`: * Seek to keep the cyclomatic complexity of functions no more than 12...

**/*.rs: * Seek to keep the cyclomatic complexity of functions no more than 12.

  • Adhere to single responsibility and CQRS

  • Place function attributes after doc comments.

  • Do not use return in single-line functions.

  • Move conditionals with >2 branches into a predicate function.

  • Avoid unsafe unless absolutely necessary.

  • Every module must begin with a //! doc comment that explains the module's purpose and utility.

  • Comments must use en-GB-oxendict spelling and grammar.

  • Lints must not be silenced except as a last resort.

    • #[allow] is forbidden.
    • Only narrowly scoped #[expect(lint, reason = "...")] is allowed.
    • No lint groups, no blanket or file-wide suppression.
    • Include FIXME: with link if a fix is expected.
  • Use rstest fixtures for shared setup and to avoid repetition between tests.

  • Replace duplicated tests with #[rstest(...)] parameterised cases.

  • Prefer mockall for mocks/stubs.

  • Prefer .expect() over .unwrap()

  • Ensure that any API or behavioural changes are reflected in the documentation in docs/

  • Ensure that any completed roadmap steps are recorded in the appropriate roadmap in docs/

⚙️ Source: CodeRabbit Configuration File

List of files the instruction was applied to:

  • tests/connection_actor.rs
🪛 GitHub Actions: CI
tests/connection_actor.rs

[error] 117-117: Clippy error: function fairness_disabled_processes_all_high_first is never used.

🔇 Additional comments (1)
tests/connection_actor.rs (1)

73-115: Well-implemented time slice fairness test.

The test correctly validates time-based queue fairness behaviour by:

  • Configuring max_high_before_low: 0 to disable count-based fairness
  • Setting a 10ms time slice
  • Carefully timing the push operations to exceed the time slice
  • Verifying that the low-priority item appears in the middle of the output sequence

The use of tokio::spawn and oneshot channel is appropriate for testing the asynchronous behaviour.

Comment on lines +77 to +79
use std::time::Duration;

use tokio::{sync::oneshot, time::sleep};
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Remove redundant imports.

The imports std::time::Duration and tokio::{sync::oneshot, time::sleep} are redundant. Duration and sleep are already imported at the module level (lines 8-9), and oneshot should be imported at the module level for consistency.

-    use std::time::Duration;
-
-    use tokio::{sync::oneshot, time::sleep};

Add oneshot to the existing tokio imports at the module level:

-use tokio::time::{Duration, sleep, timeout};
+use tokio::{sync::oneshot, time::{Duration, sleep, timeout}};
🤖 Prompt for AI Agents
In tests/connection_actor.rs around lines 77 to 79, remove the redundant imports
of std::time::Duration and tokio::{sync::oneshot, time::sleep} since Duration
and sleep are already imported at the module level. Instead, add oneshot to the
existing tokio imports at the module level for consistency and clean up
duplicate imports in this section.

@leynos
Copy link
Owner Author

leynos commented Jul 5, 2025

@coderabbitai what's causing this error?

    Checking wireframe_testing v0.1.0 (/home/runner/work/wireframe/wireframe/wireframe_testing)
error: function `fairness_disabled_processes_all_high_first` is never used
Error:    --> tests/connection_actor.rs:117:10
    |
117 | async fn fairness_disabled_processes_all_high_first(
    |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: `-D dead-code` implied by `-D warnings`
    = help: to override `-D warnings` add `#[allow(dead_code)]`

error: could not compile `wireframe` (test "connection_actor") due to 1 previous error
warning: build failed, waiting for other jobs to finish...
Error: Process completed with exit code 101.

Copy link
Contributor

coderabbitai bot commented Jul 5, 2025

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

@leynos The error is occurring because the function fairness_disabled_processes_all_high_first is defined but never called anywhere in the code. Looking at the test file, I can see that this function is missing the #[tokio::test] annotation that would make it an actual test function.

From the structure of other tests in the file, it appears this function should be annotated as a test. Here's what needs to be fixed:

#[tokio::test]
async fn fairness_disabled_processes_all_high_first(
    // ... rest of function

The function is defined but not marked as a test, so the Rust compiler sees it as dead code since it's never called. You have a few options to fix this:

  1. Add the test annotation (recommended if this should be a test):

    #[tokio::test]
    async fn fairness_disabled_processes_all_high_first(
  2. Remove the function if it's not needed

  3. Add #[allow(dead_code)] as a temporary workaround:

    #[allow(dead_code)]
    async fn fairness_disabled_processes_all_high_first(

The most likely solution is that this function should have the #[tokio::test] annotation to make it a proper test function, similar to the other test functions in the file.


🏁 Script executed:

#!/bin/bash
# Let's examine the connection_actor.rs test file to understand the context
cat tests/connection_actor.rs

Length of output: 9955


🏁 Script executed:

#!/bin/bash
# Let's also look at the specific function around line 117 to understand its structure
sed -n '110,130p' tests/connection_actor.rs

Length of output: 681


🏁 Script executed:

#!/bin/bash
# Let's search for test annotations and function patterns to understand how tests are structured
rg -A 5 -B 2 "#\[.*test.*\]" tests/connection_actor.rs

Length of output: 2529


@leynos I can see exactly what's causing the error. The function fairness_disabled_processes_all_high_first is missing the proper test annotations.

Looking at the code, all the other test functions have both #[rstest] and #[tokio::test] annotations, but this function only has:

async fn fairness_disabled_processes_all_high_first(

It should be:

#[rstest]
#[tokio::test]
async fn fairness_disabled_processes_all_high_first(

The function appears to be a legitimate test that verifies fairness behavior when fairness is disabled (with max_high_before_low: 0 and time_slice: None), ensuring all high-priority items are processed before low-priority ones.

The fix: Add the missing annotations at line 117:

#[rstest]
#[tokio::test]
async fn fairness_disabled_processes_all_high_first(
    queues: (PushQueues<u8>, wireframe::push::PushHandle<u8>),
    shutdown_token: CancellationToken,
) {
    // ... rest of the function

The #[rstest] annotation enables the function to receive the fixture parameters (queues and shutdown_token), and #[tokio::test] makes it an async test that can be discovered and run by the test framework.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant