Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update dask vine executor to new dask graphs #4015

Merged
merged 12 commits into from
Jan 17, 2025

Conversation

btovar
Copy link
Member

@btovar btovar commented Jan 8, 2025

  • make test Run local tests prior to pushing.
  • make format Format source code to comply with lint policies. Note that some lint errors can only be resolved manually (e.g., Python)
  • make lint Run lint on source code prior to pushing.
  • Manual Update: Update the manual to reflect user-visible changes.
  • Type Labels: Select a github label for the type: bugfix, enhancement, etc.
  • Product Labels: Select a github label for the product: TaskVine, Makeflow, etc.
  • PR RTM: Mark your PR as ready to merge.

@btovar btovar marked this pull request as draft January 8, 2025 16:57
@btovar btovar requested review from JinZhou5042 and dthain January 9, 2025 16:33
@btovar btovar added the TaskVine label Jan 9, 2025
@btovar btovar marked this pull request as ready for review January 9, 2025 16:33
@btovar btovar marked this pull request as draft January 9, 2025 16:46
@btovar
Copy link
Member Author

btovar commented Jan 9, 2025

Figuring out an error with coffea's CI.

@btovar btovar marked this pull request as ready for review January 9, 2025 18:20
@btovar
Copy link
Member Author

btovar commented Jan 9, 2025

Ok, it seems to be working.

@JinZhou5042
Copy link
Member

I am going to try with the new one.

Copy link
Member

@dthain dthain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The overall approach makes sense to me.

I am concerned about how we deal with backwards/forwards compatibility, esp for physics applications which have not necessarily been ported to the new version of Dask.

Do you have any ideas how to support this migration? We don't need to keep compatibility forever, but we also can't expect our key users to all change at the same time.

At the very least, we need to be very explicit in the manual about the supported version, and also note that in our Conda environments.

@btovar btovar merged commit c77ab6f into cooperative-computing-lab:master Jan 17, 2025
10 checks passed
@btovar btovar deleted the new_dask_graph branch January 17, 2025 16:24
btovar added a commit that referenced this pull request Jan 17, 2025
* DaskVine to new graph representation

* update simple graph example

* fix bug with depth

* always convert from legacy representation, for now

* check for dask in test

* do not import DaskVineDag if dask not available

* update function calls

* lint

* handle generic container graph nodes

* add warning about dask version

* example_to_revert

* remove print statement
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants