-
Notifications
You must be signed in to change notification settings - Fork 64
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
Add suds-jurko timeout support in cuahsi/wof #155
Comments
This was referenced Jun 5, 2018
I suggest the title of this issue be renamed to "Add suds-jurko timeout support in cuahsi/wof". I don't have permission to change it. |
rajadain
changed the title
Add timeout support
Add suds-jurko timeout support in cuahsi/wof
Jun 5, 2018
If y'all submit a pull request, ideally with a few tests, I can merge it in. I don't actively use the cuahsi/wof plugin. |
Addressed in PR #165. Closing. |
Ah. I forgot I didn't open this issue, so I can't close it! @dharhas, you can close this issue any time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I'm a developer for https://github.com/WikiWatershed/model-my-watershed. While working with Ulmo, at times we've felt the need to specify a custom timeout (opposed to the default 90s).
suds-jurko
supports timeouts for both the http and https modules. It would be great if they could be surfaced in the Ulmo API, just as caching currently is.Without it, we have to wrap it in a timeout decorator, which is fine for now, but limits us to single-threaded work, since it cannot handle non-pickleable responses in multithreaded environments. This wrapping is extraneous since suds does have timeout support, it's just hidden from use.
Thanks.
The text was updated successfully, but these errors were encountered: