Replace async workaround within document loader #1774
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After talking with Timo, the document loader uses a separate thread due to the fact that PyLD is synchronous code and calls
into the document loader (which requires asynchronous code). When swapping out the cache with (for example) a Redis based cache, the exception
got Future attached to a different loop
may arise due to the current separate thread/event loop based implementation.Switching to
nest_asyncio
over using a separate thread/event loop resolves the issues that were observed.