Skip to content

Conversation

@aamereller
Copy link

In some cases, especially continous or burst send applications or network reactivity tests it may come in handy to be able to cancel an ongoing transmission. For this reason additional functionality and logic supporting .NET CancellationToken functionality has been implemented . Since the native methods do not (and maybe cannot) support this only managed transmission is used when using a cancellation token, regardless whether HW acceleration is available.

@codecov
Copy link

codecov bot commented Apr 18, 2024

Codecov Report

Attention: Patch coverage is 90.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 70.76%. Comparing base (e7c4eb8) to head (9f3ed5e).
Report is 7 commits behind head on master.

Files Patch % Lines
SharpPcap/LibPcap/SendQueue.cs 90.00% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #512       +/-   ##
===========================================
- Coverage   82.81%   70.76%   -12.06%     
===========================================
  Files          51       51               
  Lines        2823     2829        +6     
  Branches      312      310        -2     
===========================================
- Hits         2338     2002      -336     
- Misses        363      715      +352     
+ Partials      122      112       -10     

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant