[telemetry] policyengine-simulation-py: KeyboardInterrupt (b659eaa2004ca456)

Aberta
#4,151 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
15/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
observability

Direção de pesquisa

This is an auto-generated telemetry report; the marked section between the telemetry-error-issues comments is rewritten daily, so add findings outside it. Start with the Logs Explorer link, which needs read access to the policyengine-observability project, and check the KeyboardInterrupt records in the 2026-10-31 window for their stack traces. Done means establishing whether these are expected shutdown signals or a real bug in policyengine-simulation-py, and recording that conclusion in the issue.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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 b659eaa2004ca456
  • 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 9 0
Affected requests 9 0
Observability IDs 9 0
Error rate on affected routes n/a n/a
Occurrences per hour 0.36 0.00
Occurrences per hour, previous 7 days 0.05 0.02
First seen in the last 8 days 2026-10-26 14:20 EDT 2026-10-26 09:09 EDT
Last seen 2026-11-01 17:06 EST 2026-10-26 14:13 EDT

Related fingerprints (sharing traces): 1a121bac81de8770

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

Linguagem predominante
Python
Estrelas
18
Forks
33
Merge médio
2d 9h
PRs com merge (30d)
77

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de PolicyEngine/policyengine-api

Todas as issues de PolicyEngine/policyengine-api

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.