Skip to content

Conversation

@ArgoZhang
Copy link
Member

@ArgoZhang ArgoZhang commented Jun 19, 2025

Link issues

fixes #6259

Summary By Copilot

Regression?

  • Yes
  • No

Risk

  • High
  • Medium
  • Low

Verification

  • Manual (required)
  • Automated

Packaging changes reviewed?

  • Yes
  • No
  • N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

  • Doc is updated/provided or not needed
  • Demo is updated/provided or not needed
  • Merge the latest code from the main branch

Summary by Sourcery

Implement delimiter-based data package handling in the TCP socket service and add corresponding unit tests.

New Features:

  • Introduce DelimiterDataPackageHandler class for parsing TCP data streams using a specified byte-delimiter.

Enhancements:

  • Add DelimiterDataPackageHandler_Ok unit test and MockDelimiterPackageAsync helper to validate delimiter-based framing.
  • Adjust port numbers in existing FixLengthDataPackageHandler unit tests to prevent conflicts.

@bb-auto bb-auto bot added the enhancement New feature or request label Jun 19, 2025
@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Jun 19, 2025

Reviewer's Guide

Introduces a new DelimiterDataPackageHandler class for splitting and processing byte-delimited data packages, augments unit tests with a corresponding test and helper, and updates existing test port numbers to avoid conflicts.

Class diagram for DelimiterDataPackageHandler and its relationship to DataPackageHandlerBase

classDiagram
    class DataPackageHandlerBase {
        <<abstract>>
        +Task ReceiveAsync(Memory<byte> data)
        +Func<byte[], Task>? ReceivedCallBack
        +Memory<byte> ConcatBuffer(Memory<byte> data)
        +void SlicePackage(Memory<byte> data, int length)
    }
    class DelimiterDataPackageHandler {
        -ReadOnlyMemory<byte> _delimiter
        +DelimiterDataPackageHandler(string delimiter, Encoding? encoding = null)
        +DelimiterDataPackageHandler(byte[] delimiter)
        +override Task ReceiveAsync(Memory<byte> data)
    }
    DataPackageHandlerBase <|-- DelimiterDataPackageHandler
Loading

Class diagram for DelimiterDataPackageHandler constructors and key members

classDiagram
    class DelimiterDataPackageHandler {
        -ReadOnlyMemory<byte> _delimiter
        +DelimiterDataPackageHandler(string delimiter, Encoding? encoding = null)
        +DelimiterDataPackageHandler(byte[] delimiter)
        +override Task ReceiveAsync(Memory<byte> data)
    }
Loading

File-Level Changes

Change Details Files
Add DelimiterDataPackageHandler class for byte‐delimited packet parsing
  • Provide constructors for string and byte[] delimiters with null checks
  • Implement ReceiveAsync: concat buffers, locate delimiter, slice packages
  • Use MemoryPool to rent buffers and invoke callback on complete packages
src/BootstrapBlazor/Services/TcpSocket/DataPackage/DelimiterDataPackageHandler.cs
Expand unit tests to cover delimiter‐based package handling
  • Add DelimiterDataPackageHandler_Ok test with mock TCP server
  • Configure client.SetDataHandler with callback to capture packets
  • Include MockDelimiterPackageAsync to simulate delimiter‐split streams
test/UnitTest/Services/TcpSocketFactoryTest.cs
Adjust test ports to prevent collisions in existing handlers
  • Change FixLengthDataPackageHandler_Ok port from 8888 to 8884
  • Change FixLengthDataPackageHandler_Sticky port from 8899 to 8885
test/UnitTest/Services/TcpSocketFactoryTest.cs

Assessment against linked issues

Issue Objective Addressed Explanation
#6259 Add a DelimiterDataPackageHandler class to handle data packages delimited by a specific byte sequence.

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

@bb-auto bb-auto bot added this to the 9.7.0 milestone Jun 19, 2025
sourcery-ai[bot]
sourcery-ai bot previously approved these changes Jun 19, 2025
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 @ArgoZhang - I've reviewed your changes and they look great!

Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments

### Comment 1
<location> `src/BootstrapBlazor/Services/TcpSocket/DataPackage/DelimiterDataPackageHandler.cs:58` </location>
<code_context>
+    {
+        data = ConcatBuffer(data);
+
+        var index = data.Span.IndexOfAny(_delimiter.Span);
+        var segment = index == -1 ? data : data[..index];
+
</code_context>

<issue_to_address>
Using IndexOfAny with a multi-byte delimiter may not match the intended delimiter sequence.

IndexOfAny matches any single byte from the delimiter, which can cause incorrect splits if the delimiter is multi-byte. Use a method that searches for the full delimiter sequence to ensure correct segmentation.
</issue_to_address>

### Comment 2
<location> `test/UnitTest/Services/TcpSocketFactoryTest.cs:177` </location>
<code_context>
     [Fact]
     public async Task FixLengthDataPackageHandler_Ok()
     {
</code_context>

<issue_to_address>
Missing edge case tests for DelimiterDataPackageHandler.

Please add tests for these edge cases: missing delimiter (data should be buffered), multiple packages in one read (callback for each), delimiter split across reads (correct reassembly), empty payloads (delimiter first), and consecutive delimiters (empty package between). This will improve robustness.
</issue_to_address>

### Comment 3
<location> `test/UnitTest/Services/TcpSocketFactoryTest.cs:298` </location>
<code_context>
+        await tcs.Task;
+
+        // 验证接收到的数据
+        Assert.Equal(receivedBuffer.ToArray(), [1, 2, 3, 4, 5, 0x13, 0x10]);
+
+        // 关闭连接
</code_context>

<issue_to_address>
Assertion order: expected and actual values should be swapped.

Swap the arguments so the expected value is first and the actual value is second: Assert.Equal([1, 2, 3, 4, 5, 0x13, 0x10], receivedBuffer.ToArray());. This improves test output clarity.
</issue_to_address>

### Comment 4
<location> `test/UnitTest/Services/TcpSocketFactoryTest.cs:280` </location>
<code_context>
+        Memory<byte> receivedBuffer = Memory<byte>.Empty;
+
+        // 增加数据库处理适配器
+        client.SetDataHandler(new DelimiterDataPackageHandler(new byte[] { 0x13, 0x10 })
+        {
+            ReceivedCallBack = buffer =>
</code_context>

<issue_to_address>
No test for string-based delimiter constructor.

Please add tests for the string-based constructor, both with and without the encoding parameter, to ensure full coverage.
</issue_to_address>

<suggested_fix>
<<<<<<< SEARCH
        // 增加数据库处理适配器
        client.SetDataHandler(new DelimiterDataPackageHandler(new byte[] { 0x13, 0x10 })
        {
            ReceivedCallBack = buffer =>
            {
                receivedBuffer = buffer;
                tcs.SetResult();
                return Task.CompletedTask;
            }
        });
=======
        // 增加数据库处理适配器
        client.SetDataHandler(new DelimiterDataPackageHandler(new byte[] { 0x13, 0x10 })
        {
            ReceivedCallBack = buffer =>
            {
                receivedBuffer = buffer;
                tcs.SetResult();
                return Task.CompletedTask;
            }
        });

        // Test: string-based delimiter constructor (default encoding)
        var tcsStringDelimiter = new TaskCompletionSource();
        Memory<byte> receivedBufferStringDelimiter = Memory<byte>.Empty;
        var stringDelimiterHandler = new DelimiterDataPackageHandler("\r\n")
        {
            ReceivedCallBack = buffer =>
            {
                receivedBufferStringDelimiter = buffer;
                tcsStringDelimiter.SetResult();
                return Task.CompletedTask;
            }
        };
        client.SetDataHandler(stringDelimiterHandler);
        await client.SendAsync(data);
        await tcsStringDelimiter.Task;
        Assert.Equal(data.ToArray(), receivedBufferStringDelimiter.ToArray());

        // Test: string-based delimiter constructor (with encoding)
        var tcsStringDelimiterEncoding = new TaskCompletionSource();
        Memory<byte> receivedBufferStringDelimiterEncoding = Memory<byte>.Empty;
        var stringDelimiterHandlerEncoding = new DelimiterDataPackageHandler("\r\n", System.Text.Encoding.UTF8)
        {
            ReceivedCallBack = buffer =>
            {
                receivedBufferStringDelimiterEncoding = buffer;
                tcsStringDelimiterEncoding.SetResult();
                return Task.CompletedTask;
            }
        };
        client.SetDataHandler(stringDelimiterHandlerEncoding);
        await client.SendAsync(data);
        await tcsStringDelimiterEncoding.Task;
        Assert.Equal(data.ToArray(), receivedBufferStringDelimiterEncoding.ToArray());
>>>>>>> REPLACE

</suggested_fix>

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.

{
data = ConcatBuffer(data);

var index = data.Span.IndexOfAny(_delimiter.Span);
Copy link
Contributor

Choose a reason for hiding this comment

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

issue (bug_risk): Using IndexOfAny with a multi-byte delimiter may not match the intended delimiter sequence.

IndexOfAny matches any single byte from the delimiter, which can cause incorrect splits if the delimiter is multi-byte. Use a method that searches for the full delimiter sequence to ensure correct segmentation.


// 关闭连接
client.Close();
StopTcpServer(server);
Copy link
Contributor

Choose a reason for hiding this comment

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

suggestion (testing): Missing edge case tests for DelimiterDataPackageHandler.

Please add tests for these edge cases: missing delimiter (data should be buffered), multiple packages in one read (callback for each), delimiter split across reads (correct reassembly), empty payloads (delimiter first), and consecutive delimiters (empty package between). This will improve robustness.

await tcs.Task;

// 验证接收到的数据
Assert.Equal(receivedBuffer.ToArray(), [1, 2, 3, 4, 5, 0x13, 0x10]);
Copy link
Contributor

Choose a reason for hiding this comment

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

nitpick (testing): Assertion order: expected and actual values should be swapped.

Swap the arguments so the expected value is first and the actual value is second: Assert.Equal([1, 2, 3, 4, 5, 0x13, 0x10], receivedBuffer.ToArray());. This improves test output clarity.

Comment on lines 279 to 288
// 增加数据库处理适配器
client.SetDataHandler(new DelimiterDataPackageHandler(new byte[] { 0x13, 0x10 })
{
ReceivedCallBack = buffer =>
{
receivedBuffer = buffer;
tcs.SetResult();
return Task.CompletedTask;
}
});
Copy link
Contributor

Choose a reason for hiding this comment

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

suggestion (testing): No test for string-based delimiter constructor.

Please add tests for the string-based constructor, both with and without the encoding parameter, to ensure full coverage.

Suggested change
// 增加数据库处理适配器
client.SetDataHandler(new DelimiterDataPackageHandler(new byte[] { 0x13, 0x10 })
{
ReceivedCallBack = buffer =>
{
receivedBuffer = buffer;
tcs.SetResult();
return Task.CompletedTask;
}
});
// 增加数据库处理适配器
client.SetDataHandler(new DelimiterDataPackageHandler(new byte[] { 0x13, 0x10 })
{
ReceivedCallBack = buffer =>
{
receivedBuffer = buffer;
tcs.SetResult();
return Task.CompletedTask;
}
});
// Test: string-based delimiter constructor (default encoding)
var tcsStringDelimiter = new TaskCompletionSource();
Memory<byte> receivedBufferStringDelimiter = Memory<byte>.Empty;
var stringDelimiterHandler = new DelimiterDataPackageHandler("\r\n")
{
ReceivedCallBack = buffer =>
{
receivedBufferStringDelimiter = buffer;
tcsStringDelimiter.SetResult();
return Task.CompletedTask;
}
};
client.SetDataHandler(stringDelimiterHandler);
await client.SendAsync(data);
await tcsStringDelimiter.Task;
Assert.Equal(data.ToArray(), receivedBufferStringDelimiter.ToArray());
// Test: string-based delimiter constructor (with encoding)
var tcsStringDelimiterEncoding = new TaskCompletionSource();
Memory<byte> receivedBufferStringDelimiterEncoding = Memory<byte>.Empty;
var stringDelimiterHandlerEncoding = new DelimiterDataPackageHandler("\r\n", System.Text.Encoding.UTF8)
{
ReceivedCallBack = buffer =>
{
receivedBufferStringDelimiterEncoding = buffer;
tcsStringDelimiterEncoding.SetResult();
return Task.CompletedTask;
}
};
client.SetDataHandler(stringDelimiterHandlerEncoding);
await client.SendAsync(data);
await tcsStringDelimiterEncoding.Task;
Assert.Equal(data.ToArray(), receivedBufferStringDelimiterEncoding.ToArray());

@codecov
Copy link

codecov bot commented Jun 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (9bd5946) to head (bf9e10f).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #6260   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          710       711    +1     
  Lines        31339     31375   +36     
  Branches      4424      4431    +7     
=========================================
+ Hits         31339     31375   +36     
Flag Coverage Δ
BB 100.00% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ArgoZhang ArgoZhang merged commit 62ed6e6 into main Jun 19, 2025
5 checks passed
@ArgoZhang ArgoZhang deleted the feat-socket branch June 19, 2025 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(DelimiterDataPackageHandler): add DelimiterDataPackageHandler class

2 participants