[2.8] Carry node state across an identity link

未关闭
#441 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
22/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
backend

调研方向

The baseline traceroute trigger is in receivers.py around lines 63-90, and that is where successor nodes must be skipped. The state carried across a link (claims, mesh_monitoring watches, DxNodeMetadata, NodeRfProfile, exposure, weather_use, m2m_opt_out, position) is not named by file, so trace it from the link code path. Start after pskillen/meshflow-api#440 (ID-2) lands. Done means no offline alert for a linked old id, no baseline traceroute or DX new-node event for a successor, and tests covering both.

由索引模型根据 Issue 内容生成。

描述

enhancement meshtastic-2.8

Part of pskillen/meshflow-api#437 (Meshtastic 2.8.x support). Code: ID-3 · Priority: Should · Size: M

Summary

When a link is made (auto or confirmed), carry over: claim and pending claims, mesh_monitoring watches (retarget + close the old node's offline state), DxNodeMetadata, NodeRfProfile, exposure, weather_use, m2m_opt_out, and inherited position.

Suppress new-node behaviour for successors: baseline traceroute (receivers.py:63-90), DX NEW_DISTANT_NODE / RETURNED_DX_NODE.

Acceptance criteria

  • No false offline alert for a linked old id
  • Claim and DX suppression survive the upgrade
  • No baseline traceroute / DX new-node event for a linked successor
  • Tests

Depends on: pskillen/meshflow-api#440 (ID-2)

主要语言
Python
星标
1
派生
0
平均合并
23 小时 9 分钟
30 天内合并 PR
15

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

pskillen/meshflow-api 的其他 Issue

查看 pskillen/meshflow-api 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。