Skip to content

fix: Supports Windows non-UTF8 encoding - #11867

Merged
yuanchaoa merged 1 commit into
v7.1from
71-fix-support-windows-non-utf8
Aug 20, 2026
Merged

fix: Supports Windows non-UTF8 encoding#11867
yuanchaoa merged 1 commit into
v7.1from
71-fix-support-windows-non-utf8

Conversation

@yuanchaoa

Copy link
Copy Markdown
Contributor

This PR is for:

  • Agent

fix: Supports Windows non-UTF8 encoding

Steps to reproduce the bug

Changes to fix the bug

Affected branches

  • main
  • 6.6
  • 7.1

Checklist

  • Added unit test to verify the fix.
  • Verified eBPF program runs successfully on linux 4.14.x.
  • Verified eBPF program runs successfully on linux 4.19.x.
  • Verified eBPF program runs successfully on linux 5.2.x.

@yuanchaoa
yuanchaoa enabled auto-merge (rebase) August 20, 2026 06:48

@kylewanginchina kylewanginchina left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Reviewed: replacing pcap::Device::list with direct pcap-sys name enumeration prevents unrelated non-UTF-8 descriptions from aborting interface discovery; list ownership is released through Drop. Required checks are tracked for merge.

@yuanchaoa
yuanchaoa merged commit e31a9a2 into v7.1 Aug 20, 2026
8 checks passed
@yuanchaoa
yuanchaoa deleted the 71-fix-support-windows-non-utf8 branch August 20, 2026 06:52
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.

2 participants