-
Notifications
You must be signed in to change notification settings - Fork 17
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
bug/coroutine-await #149
Comments
this is a more full exception stack I'm getting here |
Hi @tluthra - just want to let you know that this is on our radar! The next release of the SDK will provide much better asyncio support, and I'm chasing down these sorts of errors now. |
@awalker4 appreciate the update, until then is there anything you can suggest as a work around? |
For now, you can sidestep the async code by running with |
Also, can I see how you are calling the client? Just to make sure I can reproduce all of the asyncio warnings here. |
thanks will try that out, yea, I'm using it like this: Initializing
More or less how I'm calling it
|
Describe the bug
i'm currently using the open source version of unstructured, and getting an exception about
coroutine is being awaited already
. This causes the parse to fail, and not work.To Reproduce
It just seems to happen every so often, I'm not sure how to reproduce it. It's not on the same files, if I retry them, they'll succeed. I am putting a lot of files + data through the system, but nothing that seems to be something it shouldnt be able to handle.
Expected behavior
Not get this error.
Screenshots
N/A
Environment Info
I'm pullling
downloads.unstructured.io/unstructured-io/unstructured-api:latest
as my container and just running this.Also running
unstructured-client = "^0.23.8"
on my client side.Additional context
There's also a few warning that are showing up related to coroutines too:
The text was updated successfully, but these errors were encountered: