Skip to content

subsecond scheduling for "@every" #534

@gezimblliku

Description

@gezimblliku

Since subsecond scheduling is not supported even when using @ every, I forked the subject to remove the second limit (mostly to prevent long unit tests).
I wanted to know the reason why this limitation is added first place,to prevent any degradation of performance or any potential misschedule of jobs?

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