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

TaskVine vs threadpoolctl import error reporting #3608

Open
benclifford opened this issue Sep 6, 2024 · 0 comments
Open

TaskVine vs threadpoolctl import error reporting #3608

benclifford opened this issue Sep 6, 2024 · 0 comments

Comments

@benclifford
Copy link
Collaborator

Describe the bug

TaskVine installed from source starts needing threadpoolctl at commit 0d3c115b082f3f6e365385d7602c923b676a9a3f

pytest of taskvine with this config:

from parsl.config import Config
from parsl.data_provider.file_noop import NoOpFileStaging
from parsl.data_provider.ftp import FTPInTaskStaging
from parsl.data_provider.http import HTTPInTaskStaging
from parsl.executors.taskvine import TaskVineExecutor, TaskVineManagerConfig


def fresh_config():
    return Config(executors=[TaskVineExecutor(manager_config=TaskVineManagerConfig(port=9000, shared_fs=True),
                                              worker_launch_method='factory', function_exec_mode='serverless')])

stops working at that commit and instead hangs.

It doesn't log anything that I could find about needing threadpoolctl.

This shouldn't be a problem when installing from proper packaging - but more generally I think it is a problem that some internal piece is breaking and hanging, and that same situation may arise for other more relevant errors.

To Reproduce
Use TaskVine at that commit above with the supplied config file, and make sure threadpoolctl is not installed with pip

Expected behavior
proper shutdown with error message leading the user towards the problem

Environment
my laptop

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

No branches or pull requests

1 participant