fix(isotp): wake receivers when the reader fails on an exception the generic-catch filter excludes

[dborgards]

Potential fix for https://github.com/dborgards/CanKit.Pro/security/code-scanning/468

Use a filtered catch instead of a fully generic catch in RunReaderAsync so only non-fatal exceptions are treated as subscription loss.

Best fix in this snippet:

• In src/CanKit.Pro.IsoTp/IsoTpChannel.cs, within RunReaderAsync, replace:
  • catch (Exception ex)
• With:
  • catch (Exception ex) when (ex is not OutOfMemoryException and not StackOverflowException and not AccessViolationException and not AppDomainUnloadedException and not BadImageFormatException and not CannotUnloadAppDomainException and not ThreadAbortException)

Why this is best here:

• Keeps existing behavior for expected runtime failures (still captures and propagates them as lost).
• Avoids catching critical/fatal exceptions that should not be handled as normal subscription loss.
• Requires no new imports, no structural refactor, and minimal code change localized to the flagged region.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

[cursor]

PR Summary

Medium Risk
Changes exception handling on the ISO-TP subscription reader thread, which gates all inbound traffic and ReceiveAsync completion; behavior is tightened for rare fatal exceptions but is covered by new tests.

Overview
Addresses code-scanning alert on a generic catch in RunReaderAsync by using exception filters so only non-fatal subscription failures are handled like ordinary “subscription lost” errors.

For fatal reader failures (e.g. OutOfMemoryException, BadImageFormatException) that must not be swallowed, the reader now publishes inbox loss first via a new PublishSubscriptionLoss helper, then rethrows so ReceiveAsync waiters and later receives still see the same fault and the background reader task still faults (fixing a hang when those exceptions bypassed loss signaling).

Adds an integration theory test that simulates excluded reader failures and asserts both concurrent and subsequent receives, BackgroundExceptionOccurred, and _readerTask all observe the same exception instance.

^{Reviewed by Cursor Bugbot for commit c660fd2. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-03T16:22:26.803451Z	178a801	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 178a801920

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!