dbader / dbader/schedule

Loop check or wait to that timestamp?

Open
#180 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
12.3k
Forks
999
PR merge metrics
No merged PRs in 30d

Description

How about we calculate the most recent job and wait to that point. ( thread sleep or sth etc.)
Looks like It's more effective than loop check.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files or tests. Start by locating the scheduler loop that performs the current loop check and review how the most recent job timestamp is calculated; done means the scheduler waits for that point and existing behavior remains covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.