Skip to content

fix: api key adding stuck when ollama dependency not installed. - #46

Merged
beersoccer merged 2 commits into
beersoccer:mainfrom
sususweet:fix/ollama-stuck-issue
Apr 29, 2026
Merged

beersoccer merged 2 commits into
beersoccer:mainfrom
sususweet:fix/ollama-stuck-issue

Conversation

@sususweet

@sususweet sususweet commented Apr 23, 2026 •

Copy link
Copy Markdown

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.
image

@sususweet
sususweet force-pushed the fix/ollama-stuck-issue branch from 11b7713 to 9a4e804 Compare April 23, 2026 02:38
@beersoccer
beersoccer merged commit 58a0d3b into beersoccer:main Apr 29, 2026
4 checks passed
@beersoccer

Copy link
Copy Markdown
Owner

Thanks for the clear diagnosis and clean fix! Already merged.

@sususweet
sususweet deleted the fix/ollama-stuck-issue branch April 29, 2026 06:13
sususweet pushed a commit to sususweet/mem0_dify_plugin that referenced this pull request Jun 3, 2026
- Bump version to 0.3.1 across manifest.yaml and pyproject.toml
- Update CHANGELOG and README with v0.3.1 release notes

Changes included (from PRs beersoccer#46 and beersoccer#47 by sususweet):
- Fix psycopg3 connection errors on Windows (gevent/ProactorEventLoop conflict)
- Add WindowsSelectorEventLoopPolicy on win32 at plugin startup
- Conditional psycopg deps: psycopg3 on Linux/macOS, psycopg2 on Windows
- Raise WRITE_OPERATION_TIMEOUT 15s → 45s to reduce silent write failures
- Add missing ollama dependency to pyproject.toml

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants