Skip to content

Conversation

@jedcunningham
Copy link
Member

When the DAG processor resorts its file queue by modification time (e.g., after a bundle refresh), files with pending callbacks could lose their position at the front of the queue. This could delay callback execution (like DAG failure callbacks) if those files happened to have older modification times.

The fix partitions the queue during resort: callback files stay at the front in their original order, while only regular files are sorted by mtime.


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

Generated-by: Cursor (Clause Opus 4.5)

When the DAG processor resorts its file queue by modification time
(e.g., after a bundle refresh), files with pending callbacks could
lose their position at the front of the queue. This could delay
callback execution (like DAG failure callbacks) if those files
happened to have older modification times.

The fix partitions the queue during resort: callback files stay at
the front in their original order, while only regular files are
sorted by mtime.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants