You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently lage only gives a package graph and task graph separately, so task-scheduler doesn't know when some packages do not contain the tasks in the package.json.
Because of how the final combined package-task is generated, we might over-aggressively run tasks because of this missing info.
For example, if A depends on B and B depends on C:
A -> B -> C
and if only C has the task of special-C-build, when this following is called:
lage special-C-build --scope A
Nothing should be run because "A" doesn't have that task. The expected result is that nothing is run.
This task is to modify the api to accept the info for if a task can be run inside package
The text was updated successfully, but these errors were encountered:
This task is linked to microsoft/lage#104.
Currently lage only gives a package graph and task graph separately, so task-scheduler doesn't know when some packages do not contain the tasks in the package.json.
Because of how the final combined package-task is generated, we might over-aggressively run tasks because of this missing info.
For example, if A depends on B and B depends on C:
A -> B -> C
and if only C has the task of special-C-build, when this following is called:
lage special-C-build --scope A
Nothing should be run because "A" doesn't have that task. The expected result is that nothing is run.
This task is to modify the api to accept the info for if a task can be run inside package
The text was updated successfully, but these errors were encountered: