[telemetry] policyengine-simulation-py: KeyboardInterrupt (25af6596251093a8)

未關閉
#4,153 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
半天
新手友好度
18/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
python
領域
backend

研究方向

The payload names no source file or test; it is a telemetry report for KeyboardInterrupt in the policyengine-simulation-py service, with no route. Start with the matching log records behind the Logs Explorer link, which needs read access to the policyengine-observability project, to see what was running when the interrupt occurred. Done means the cause is identified and either the interrupt is handled as expected or a fix is proposed, and the maintainers agree on which.

由索引模型根據 Issue 內容生成。

描述

service: policyengine-simulation-py telemetry-error

The daily telemetry error report opened this issue for a production error group. Each run replaces the marked section below with the latest day's measures; text outside it is kept.

Error group 25af6596251093a8
  • Kind: exception (fingerprint algorithm 2)
  • Service: policyengine-simulation-py
  • Exception type: KeyboardInterrupt
  • Most frequent route: -
  • Window: 2026-11-01 00:00 EDT to 2026-11-02 00:00 EST (25 hours)
Measure Production Staging
Occurrences 3 0
Affected requests 3 0
Observability IDs 3 0
Error rate on affected routes n/a n/a
Occurrences per hour 0.12 0.00
Occurrences per hour, previous 7 days 0.01 0.00
First seen in the last 8 days 2026-10-31 09:45 EDT n/a
Last seen 2026-11-01 17:05 EST n/a

Related fingerprints: none

Matching log records in Logs Explorer, for the window only. It needs read access to the policyengine-observability project.

主要語言
Python
星號
18
分支
33
平均合併
2 天 21 小時
30 天內合併 PR
93

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

PolicyEngine/policyengine-api 的其他 Issue

查看 PolicyEngine/policyengine-api 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。