fix: restore index back when continue process #85
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
|
60 seconds works nicely for me. So I add that change to this pull request too |
|
Oh nice, thank you, definitely |
dartpain
approved these changes
Feb 14, 2023
This pull request was closed.
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.
I don't know why there needs to be a
store.index = None, but I got an error when continuing the process, so I restored the index before continuing;But that's only fixed the index issue.
Another problem is there is no error catch for the
store.add_texts([i.page_content], metadatas=[i.metadata])in theexceptblock, so if 10 seconds is not enough (maybe set it to 60?), then the second error will be thrown out, and this time, notry/exceptfor this one