Skip to content

Conversation

@ArgoZhang
Copy link
Member

@ArgoZhang ArgoZhang commented Jul 27, 2025

Link issues

fixes #6495

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

Ensure DefaultNetworkMonitorService always releases its semaphore by wrapping the initialization logic in a try/finally and removing redundant Release calls.

Bug Fixes:

Enhancements:

  • Move network module loading into the try block and consolidate semaphore release in the finally clause to simplify logic

@bb-auto bb-auto bot added the enhancement New feature or request label Jul 27, 2025
@bb-auto bb-auto bot added this to the 9.8.0 milestone Jul 27, 2025
@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Jul 27, 2025

Reviewer's Guide

Ensure the semaphore is always released by wrapping the network module initialization in a try/finally and removing the redundant release outside the block.

Sequence diagram for semaphore handling in RegisterStateChangedCallback

sequenceDiagram
    participant Component
    participant DefaultNetworkMonitorService
    participant SemaphoreSlim
    participant NetworkModule
    Component->>DefaultNetworkMonitorService: RegisterStateChangedCallback()
    DefaultNetworkMonitorService->>SemaphoreSlim: WaitAsync(3000)
    alt !_init
        DefaultNetworkMonitorService->>DefaultNetworkMonitorService: try
            DefaultNetworkMonitorService->>NetworkModule: LoadModuleByName("net")
            NetworkModule-->>DefaultNetworkMonitorService: Module instance
            DefaultNetworkMonitorService->>NetworkModule: InvokeVoidAsync("init", ...)
        DefaultNetworkMonitorService->>SemaphoreSlim: finally Release()
    else _init
        DefaultNetworkMonitorService->>SemaphoreSlim: Release()
    end
Loading

File-Level Changes

Change Details Files
Wrap initialization logic in try/finally to guarantee semaphore release
  • Added try/finally around _init flag set and network module loading
  • Moved _semaphoreSlim.Release() into the finally block
  • Removed the standalone release call after the if-statement
src/BootstrapBlazor/Services/DefaultNetworkMonitorService.cs

Assessment against linked issues

Issue Objective Addressed Explanation
#6495 Refactor NetworkMonitor to ensure SemaphoreSlim is always released using a try/finally block.

Possibly linked issues


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

@ArgoZhang ArgoZhang merged commit b02aca8 into main Jul 27, 2025
4 checks passed
@ArgoZhang ArgoZhang deleted the refactor-nt branch July 27, 2025 01:07
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/DefaultNetworkMonitorService.cs:61` </location>
<code_context>
             if (!_init)
             {
-                _init = true;
+                try
+                {
+                    _init = true;

-                _networkModule ??= await _runtime.LoadModuleByName("net");
-                await _networkModule.InvokeVoidAsync("init", new
+                    _networkModule ??= await _runtime.LoadModuleByName("net");
+                    await _networkModule.InvokeVoidAsync("init", new
+                    {
+                        Invoke = _interop,
+                        OnNetworkStateChangedCallback = nameof(TriggerNetworkStateChanged)
+                    });
+                }
+                finally
                 {
-                    Invoke = _interop,
</code_context>

<issue_to_address>
The try/finally block now only releases the semaphore if _init was false.

If _init is true, the semaphore is not released, which may cause deadlocks on subsequent RegisterStateChangedCallback calls. Ensure _semaphoreSlim.Release() is always called to prevent this.
</issue_to_address>

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.

Comment on lines +61 to +70
try
{
_init = true;

_networkModule ??= await _runtime.LoadModuleByName("net");
await _networkModule.InvokeVoidAsync("init", new
_networkModule ??= await _runtime.LoadModuleByName("net");
await _networkModule.InvokeVoidAsync("init", new
{
Invoke = _interop,
OnNetworkStateChangedCallback = nameof(TriggerNetworkStateChanged)
});
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): The try/finally block now only releases the semaphore if _init was false.

If _init is true, the semaphore is not released, which may cause deadlocks on subsequent RegisterStateChangedCallback calls. Ensure _semaphoreSlim.Release() is always called to prevent this.

@codecov
Copy link

codecov bot commented Jul 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@c3eba6b). Learn more about missing BASE report.
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff            @@
##             main     #6496   +/-   ##
========================================
  Coverage        ?   100.00%           
========================================
  Files           ?       714           
  Lines           ?     31387           
  Branches        ?      4431           
========================================
  Hits            ?     31387           
  Misses          ?         0           
  Partials        ?         0           
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.

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.

refactor(NetworkMonitor): add try/finally keep release simaphore slim

2 participants