bug(ingest): telemetry without a time field is rejected with 400

已关闭
  • 哪里不对？
#478 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

已经有一个关联 PR 被合并了。

  • #483 来自 @pskillen —— 已合并

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
api, backend

调研方向

Start by tracing the ingest serializer that requires telemetry.time and the telemetry models that determine whether the reading time can be null. Check how rx_time or the observation time is handled for other telemetry fields. Done means packets without time are stored using an allowed fallback or null, and the endpoint no longer rejects them with HTTP 400.

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

描述

bug

Problem

The ingest endpoint rejects some telemetry packets with HTTP 400 {"decoded":{"telemetry":{"time":["This field is required."]}}}. Feeders hit this about once an hour. In pre-prod on 2026-11-04, PDYt and PDYb both got it on the same packet at 08:35:06, and there were 12 earlier occurrences the same day. The packet is dropped, so the telemetry is lost.

Meshtastic doesn't guarantee telemetry.time: a node without a valid clock sends 0 or omits it. The serializer makes it required.

Expected

A telemetry packet without time is stored. Use the packet's rx_time (or the observation's) as the reading time, or leave it null, whichever the telemetry models allow. It must not be rejected.

Notes

  • Seen on main before the Meshtastic 2.8 work. It's not a regression.
  • The bot logs it as StorageAPI.store_raw_packet - HTTP error storing packet.
  • Related: #436 (ingest correctness review).
主要语言
Python
星标
1
派生
0
平均合并
11 小时 33 分钟
30 天内合并 PR
52

环境准备

  • 提供 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 摘要。