Skip to content

fix(protocols): correct 'timestmap' and 'movile' in two messages (#2171) - #2189

Merged
JarryShaw merged 1 commit into
mainfrom
fix/2171-timestamp-mobile-typos
Oct 25, 2026
Merged

JarryShaw merged 1 commit into
mainfrom
fix/2171-timestamp-mobile-typos

Conversation

@JarryShaw

Copy link
Copy Markdown
Owner

What is the purpose of your pull request?

  • fix — corrects a defect

Description

Closes #2171.

  • Fix: "timestmap" becomes "timestamp" in the IPv4 timestamp-flag warning (pcapkit/protocols/schema/internet/ipv4.py), and "movile" becomes "mobile" in the MH mobile network prefix error (pcapkit/protocols/internet/mh.py). A grep finds no other copies.
  • Test: tests/protocols/internet/test_message_spelling_2171_unit.py. On main both cases fail, e.g. 'unknown timestamp flag: 2' not found in '… unknown timestmap flag: 2'.
  • Tests run: the new test, test_ipv4_unit, test_mh_unit and the tier guard pass (213).
  • Overlap: docs(protocols): fifth whole-repo pass over internet (#1103) #2155 also edits mh.py; the two merge cleanly.

TSOption.post_process warned of an "unknown timestmap flag", and
MH._make_opt_mnp raised on an "invalid movile network prefix".

Spell them "timestamp" and "mobile".

Test: test_message_spelling_2171_unit packs a timestamp option with
flag 2 and builds a mobile network prefix option from an IPv4 prefix,
and checks each message's spelling.
@JarryShaw JarryShaw added bug Issues reporting a defect (set by the bug report template; a default, not an assessment) review: running A cross-review is in flight against the current head - no verdict yet labels Oct 25, 2026
@JarryShaw

Copy link
Copy Markdown
Owner Author

Review: GOOD TO GO at 81bda3cc3 (Sonnet): no other copy of either typo in the repo, nothing pins the old text, both cases fail on main through the real code paths, and a spelling pass over both files found nothing else.

@JarryShaw JarryShaw added review: good-to-go Cross-review at the current head says ready; CI state is separate and removed review: running A cross-review is in flight against the current head - no verdict yet labels Oct 25, 2026
@JarryShaw JarryShaw moved this to In review in PyPCAPKit Oct 25, 2026
@JarryShaw

Copy link
Copy Markdown
Owner Author

Ready to merge at 81bda3cc3. Merging closes #2171.

  • Review: Sonnet GOOD TO GO.
  • CI: Required checks passed SUCCESS, 0 failed. Only the board's Sync Status is still open.
  • KTLO: 12 legs, no warnings.
  • Ordering: protocols/internet leg merged into main: 723 tests, 0 failures.

@github-actions

Copy link
Copy Markdown
Contributor

Coverage: 91.55% (unit tier, Python 3.15, 81bda3cc3, Unit Tests run success)

Package Statements Missed Branches Partial Cover
pcapkit (top level) 104 4 20 2 95.16%
pcapkit/const 19599 880 2618 866 92.12%
pcapkit/corekit 2589 75 816 37 96.48%
pcapkit/dumpkit 282 3 102 3 98.44%
pcapkit/foundation 2971 23 1036 25 98.80%
pcapkit/interface 138 4 52 3 96.32%
pcapkit/protocols 17418 219 4574 185 98.14%
pcapkit/toolkit 869 36 298 10 95.20%
pcapkit/utilities 504 7 146 5 98.15%
pcapkit/vendor 4432 1988 1018 167 51.87%

Per-file detail: the coverage-html artifact of this run.

@JarryShaw
JarryShaw merged commit 0d0783a into main Oct 25, 2026
65 checks passed
@github-project-automation github-project-automation Bot moved this from In review to Done in PyPCAPKit Oct 25, 2026
@JarryShaw
JarryShaw deleted the fix/2171-timestamp-mobile-typos branch October 25, 2026 14:50
@JarryShaw JarryShaw removed the review: good-to-go Cross-review at the current head says ready; CI state is separate label Oct 25, 2026
@JarryShaw JarryShaw added this to the PyPCAPKit v1.5 milestone Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Issues reporting a defect (set by the bug report template; a default, not an assessment)

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

fix(protocols): correct 'timestmap' and 'movile' in IPv4 and MH messages

1 participant