scheduler

Description

I am suggesting adding support for these filters for datetime objects when browsing airflow objects in the UI:

• greater than or equal to
• less than or equal to

Use case/motivation

When viewing DagRuns under the browse menu for example (Browse -> DagRuns), then only less than or greater than filters are available for filtering on datetime objects and since many logical

Summary

"This is pretty confusing: are the types here config types? the types of the resource? if the former, they don't seem right; if the latter, it's not helpful to have Any for essentially any meaningful resource -- we should either allow the user to give us a hint of what type the resource is, or cut this f

Is there a way to make a job re-occur N milliseconds after it finished previous time?

The tests fail sometimes due to millisecond based timing on some of the tests. I over optimized for local testing and it's causing tests to fail in CI occasionally. The CI pipeline is running in docker with limited resources, so not able to handle quite as precise time as my local machine.