You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(pcapng): an NRB record whose name list ends in empty names loses them on rebuild #1383
An NRB record with data a\0\0 or a\0b\0 does not rebuild byte-exactly: the parse strips trailing NULs, so empty names vanish. main behaves identically. The spec has an open issue about empty strings, so decide whether to keep them. Either way, the raw record bytes must round-trip.
Confirmed by the #1373/#1378 cross-reviews; present on main too, so not a regression of those PRs. Blocked until#1373 and #1378 merge (same PCAP-NG/PCAP modules).
Still blocked, now on a different PR.#1378 has merged, but the PCAP-NG half of #1398 (#1325, strict option lengths) is about to edit the same PCAP-NG files. Blocked until#1398 merges.
Unblocked:#1398 (and #1400) have merged. One worker is taking all the PCAP-NG follow-ups together, #1382–#1384, #1401, #1405 and #1406, because they edit the same pcapng.py files.
Activity
JarryShaw commentedon Oct 8, 2026
Still blocked, now on a different PR. #1378 has merged, but the PCAP-NG half of #1398 (#1325, strict option lengths) is about to edit the same PCAP-NG files. Blocked until #1398 merges.
JarryShaw commentedon Oct 8, 2026
Unblocked: #1398 (and #1400) have merged. One worker is taking all the PCAP-NG follow-ups together, #1382–#1384, #1401, #1405 and #1406, because they edit the same
pcapng.pyfiles.fix(pcapng)!: PCAP-NG round-trip follow-ups (#1382, #1383, #1384, #1401…