Event metadata has no size limit of its own

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start by locating request validation for POST /api/v1/tracking/track and /tracking/batch, then trace where stored event metadata is read by analysis and exports. Define the per-event size and depth limits with those consumers in mind. Done means requests exceeding either limit return 422 and name metadata, the tracking API documentation states both limits, and focused specs cover the behavior.

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

描述

enhancement post-launch

An event's metadata (on POST /api/v1/tracking/track and /tracking/batch) has no size limit of its own. Since 0.26.2 every request body is limited to 5 MiB, which bounds it per request, but a single event can still carry metadata up to that size, and it is stored and later read by analysis.

Wanted: a documented per-event metadata limit (size and depth), chosen with the analysis paths that read metadata in mind, refused with 422 naming the field, and stated in the tracking API docs. Needs its own small spec first, because analysis and exports read the stored metadata.

主要语言
Python
星标
0
派生
4
平均合并
5 小时 36 分钟
30 天内合并 PR
509

环境准备

从这里开始

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

Controlvar/controlvar 的其他 Issue

查看 Controlvar/controlvar 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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