Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

style: limit durabletask warnings for timers

Fechada
#980 4 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 2 dias

@manduinca já está trabalhando nisso.

Desde 13/9/2026.

  • #1210 de @manduinca — aberto

Avaliação

Esta issue ainda não foi avaliada.

Descrição

good first issue

Expected Behavior

I have a workflow with external events, I have a timer configured for a timeout as seen below. I could not confirm if this is the root of all of the logs that I got, but my expected behavior is that if an unexpected timer is fired to not spam my logs.

wf_completion_event = ctx.wait_for_external_event(event_name)
timeout_event = ctx.create_timer(timedelta(hours=24))
winner = yield when_any([wf_completion_event, timeout_event])

Actual Behavior

I do not have the steps to reproduce this issue, but the couple of times it happened were after an activity had retried. My logs are spammed with +1k lines of warnings (snippet below) from a single request. Not sure if this is due to the timer I configured or something else.

2026-04-09 15:33:35.150 durabletask-worker WARNING: ac1d3d89-d79b-4d07-b86e-1f9d7d636081:0001: Ignoring unexpected timerFired event with ID = 5.
2026-04-09 15:33:35,150 - durabletask-worker - WARNING - ac1d3d89-d79b-4d07-b86e-1f9d7d636081:0001: Ignoring unexpected timerFired event with ID = 5.
2026-04-09 15:33:35.150 durabletask-worker WARNING: ac1d3d89-d79b-4d07-b86e-1f9d7d636081:0001: Ignoring unexpected timerFired event with ID = 5.
2026-04-09 15:33:35,150 - durabletask-worker - WARNING - ac1d3d89-d79b-4d07-b86e-1f9d7d636081:0001: Ignoring unexpected timerFired event with ID = 5.
2026-04-09 15:33:35.150 durabletask-worker WARNING: ac1d3d89-d79b-4d07-b86e-1f9d7d636081:0001: Ignoring unexpected timerFired event with ID = 5.
2026-04-09 15:33:35,150 - durabletask-worker - WARNING - ac1d3d89-d79b-4d07-b86e-1f9d7d636081:0001: Ignoring unexpected timerFired event with ID = 5.

acceptance criteria:

  • this log is only logged once and is not contained within a loop that can spam our end users

Steps to Reproduce the Problem

I do not know how to reproduce the error, apologies!

Release Note

RELEASE NOTE:

Linguagem predominante
Python
Estrelas
274
Forks
157
Merge médio
5d 20h
PRs com merge (30d)
71

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

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 dapr/python-sdk

Todas as issues de dapr/python-sdk

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.