Skip to content

Handle dependencies in legacy dictionary task values - #12611

Open
abhisek343 wants to merge 3 commits into
dask:mainfrom
abhisek343:fix/legacy-dict-task-dependencies
Open

abhisek343 wants to merge 3 commits into
dask:mainfrom
abhisek343:fix/legacy-dict-task-dependencies

Conversation

@abhisek343

Copy link
Copy Markdown

"Client.get()" currently fails to resolve dependencies referenced inside dictionary values in legacy task graphs. Lists and tuples are converted recursively, but dictionaries are not, so graph keys nested in dict values remain literal strings instead of becoming dependencies.

This change recursively converts dictionary values during legacy task conversion while keeping dictionary keys literal.

The regression test covers:

  • direct dictionary values referencing graph keys
  • dependencies nested inside lists within dictionaries
  • dictionary keys that happen to match graph keys remaining unchanged

@github-actions

Copy link
Copy Markdown
Contributor

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

     25 files  +     1       25 suites  +1   7h 4m 58s ⏱️ + 7m 38s
 19 915 tests +     1   18 482 ✅ +     1   1 433 💤 ±    0  0 ❌ ±0 
379 377 runs  +18 478  332 107 ✅ +17 249  47 270 💤 +1 229  0 ❌ ±0 

Results for commit 25b4932. ± Comparison against base commit 9dc535d.

This branch has not been deployed

No deployments
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.

Client.get doesn't evaluate dependency if it's in dictionary value or nested inside dictionary

1 participant