Skip to content

Conversation

@trulede
Copy link
Contributor

@trulede trulede commented Nov 4, 2025

When a task(s) is watched, and a watched event occurs, then; the current context is cancelled (which signals the task and sub-tasks), then the watch conditions are evaluated, and finally if the watch conditions are satsified, then the task(s) are restarted.

This means that if a watch condition is not satisified (i.e. "skipped for file not in sources") then the task is cancelled and not restarted.

In this PR the logic is altered as follows: First the watch condition is evaluated, if at least one task(s) satisifies the condition then all tasks are cancelled, and then all tasks restarted. When no task satisified the watch contition, no action is taken. Given the way this code behaves, I believe its an improvement within the scope of the known limitations of the method used (i.e. the Context object).

closes #2477

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Watch hijacking dependency process

1 participant