-
Notifications
You must be signed in to change notification settings - Fork 195
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
bad poncho import error message in Task Vine #3552
Comments
Hmm, I wonder what the precise installation method is here. @BarrySlyDelgado is Mr Poncho. Do you have any other ideas? |
yeah it's my dev source build! if i pip install conda_pack then I get the right behaviour and can run stuff - so it's really the phrasing rather than any fundamental failure here... |
So maybe we should not try so hard to catch the error, and just let the import fail in the normal way. There was some prior reason we did it that way, but the reason eludes me... |
yeah i think that would be good. there are other places in parsl where we have done an import and made the assumption that the |
alternatively, what I did to diagnose above was to write this: catch ImportError as ie which makes the stack trace contain the original exception rather than masking it. I'm not super fussed either way, and if you don't get round to doing anything here, i'll probably commit that (with a message rephase) when I'm feeling like a simple PR... |
We now forgo catching the import exception when creating a library with the change introduced in cooperative-computing-lab/cctools#3907 |
Describe the bug
Trying to use Task Vine serverless mode, I get an error:
"The poncho module is not available. Cannot create library {name}."
On deeper investigation, this is actually masking a different error, that
conda_pack
is not importable - see the below stack trace from lightly hacked code.This is misleading to users who do have poncho available and are trying to debug this.
cc @tphung3 @dthain
To Reproduce
install task vine without conda pack. try using serverless mode.
Environment
my laptop
The text was updated successfully, but these errors were encountered: