fix: LlamaIndex compatibility fix #1940
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
axiomofjoy
approved these changes
Dec 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
resolves #1931
Compatibility fixes for LlamaIndex. Bumps the minimum LlamaIndex version to 0.9.14.
Some type definitions have moved, and the way our patching interacts with LlamaIndex code has changed. Even though our behavior tests still seem to work, patching
LLMPredictorinMockServiceContextdoesn't seem to have the behavior we think it does anymore so indirect assertions on the patching behavior have broken. For now I'm inverting the assertion as documentation that we should investigate our testing strategy.