Skip to content

sleep 1.2 when interval is 1 should be "missed" #1

@szabgab

Description

@szabgab

Hi, my understanding of "running every second" is that if one task takes more than 1 second (e.g. 1.2) then it should me marked as "missed". Right now it seems it is only marked missed if the job takes more than 2 seconds or when the accumulated delay is more than 1 second. (as seen in examples/intervals_missed.py)

Was this the intention?

Thinking about it further, maybe there need to be two indicators. One is to indicate that an iteration has missed its expected starting time, what was my understanding. Another one to indicate when it started after it was supposed to be already finished, which seems to be the current behavior.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions