fix: api key adding stuck when ollama dependency not installed.#46
Merged
Conversation
sususweet
force-pushed
the
fix/ollama-stuck-issue
branch
from
11b7713 to
9a4e804
Compare
Owner
|
Thanks for the clear diagnosis and clean fix! Already merged. |
3 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When ollama dependency is not installed and user sets llm API key to ollama provider, this plugin will stuck at the step adding API key. The reason is that the ollama dependency in mem0 chooses to wait user's input to determine whether to install this plugin.
