Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Design: Include JS errors in TinyPilot debug logs

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
javascript, python

调研方向

No files, tests, or entry points are identified. Start by resolving the storage and log-rotation approach, the backend endpoint, and browser error capture; done means client-side JavaScript errors are received by the backend and included in rotated TinyPilot debug logs.

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

描述

enhancement

The current TinyPilot debug logs are all from logs on the device itself, so we don't see errors that occurred in the client's browser.

In some cases, it would be helpful for diagnosing a customer's issue if we could see the contents of their JS console error log.

This is nontrivial, as there are a few issues to solve:

  • Where do we store JS logs to ensure they get properly logrotated?
  • What does the backend endpoint look like for receiving JS errors?
  • How do we trigger the web app to send JS errors to the backend?
    • I don't know how to do it, but there are a ton of JS error monitoring platforms (e.g., Sentry) that seem to hook into the browser's error handler, so I'm pretty sure there's some way of grabbing JS errors.
主要语言
Python
星标
3.5k
派生
292
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

tiny-pilot/tinypilot 的其他 Issue

查看 tiny-pilot/tinypilot 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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