Skip to content

feat(meshcore): enrich heard resolved_path with segment lookup and auto-matcher#395

Merged
pskillen merged 2 commits into
mainfrom
api-311/pskillen/mc-heard-path-resolution
Jun 4, 2026
Merged

feat(meshcore): enrich heard resolved_path with segment lookup and auto-matcher#395
pskillen merged 2 commits into
mainfrom
api-311/pskillen/mc-heard-path-resolution

Conversation

@pskillen
Copy link
Copy Markdown
Owner

@pskillen pskillen commented Jun 4, 2026

Summary

  • Key heard[] path hop resolution by (hash_mode, hash_size, segment_hash) when loading MeshCorePathSegmentResolution rows.
  • Expose path_hash_mode and path_hash_size on each MeshCoreHeardObservation.
  • Add guarded suffix auto-matcher for unresolved segments: unique match → resolved with short_name and position; multiple → ambiguous with candidates[].
  • Update OpenAPI ResolvedHop and traceroute ADR addendum.
  • Docs: packet-path-tracing progress/outstanding/bug-no-path-info (tier-1/tier-2 status, GI7ULG pre-prod notes).

Testing performed

  • pytest meshcore_packets/tests/test_path_resolution.py text_messages/tests/test_heard_api.py
  • Deploy API and verify MeshCore message heard[].resolved_path on pre-prod (e.g. GI7ULG test message)

Deploy before meshflow-ui#322.

Related: meshflow-ui#311

…to-matcher

Key heard[] hops by hash_mode, hash_size, and segment_hash; add short_name,
candidates on ambiguous suffix matches, and path_hash metadata on observations.
Record tier-1/tier-2 PR status, GI7ULG pre-prod findings, and heard
sender UX fix; clarify empty path_hashes vs resolution gaps.
@pskillen pskillen merged commit 18602fd into main Jun 4, 2026
2 checks passed
@pskillen pskillen deleted the api-311/pskillen/mc-heard-path-resolution branch June 4, 2026 12:25
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