Skip to content

Don't use dask delayed for regular python type return values #182

@seibert

Description

@seibert

There is a branch that builds Dask tasks for algorithms in one of two ways, depending on whether the return value is a registered concrete type, or a python type:

https://github.com/metagraph-dev/metagraph/blob/main/metagraph/core/dask/resolver.py#L215-L230

This doesn't seem to be necessary and will make visualization and analysis harder. The result should always be a Placeholder object.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions