mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
slack bot requirement conflict #933
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @fatelei on GitHub (Jan 13, 2026).
Self Checks
Dify version
1.11.2
Plugin version
0.0.4
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
install slack bot plugin
✔️ Error log
failed to launch plugin: failed to install dependencies: failed to install dependencies: exit status 1, output: DEBUG uv 0.9.13 (7ca92dcf6 2025-11-26) TRACE Checking shared lock for
/Users/fatelei/.cache/uvat/Users/fatelei/.cache/uv/.lockDEBUG Acquired shared lock for/Users/fatelei/.cache/uvDEBUG Searching for default Python interpreter in virtual environments DEBUG Failed to inspect Python interpreter from active virtual environment atcwd/langgenius/slack-bot-0.0.4@c3d4158d2511a4c05c3869b5e27b...in==0.5.0, we can conclude that you require werkzeug>=3.0.3,<3.1.dev0. And because you require werkzeug==3.1.5, we can conclude that your requirements are unsatisfiable. DEBUG Released lock at/Users/fatelei/go/src/github.com/fatelei/dify-plugin-daemon/cwd/langgenius/slack-bot-0.0.4@c3d4158d2511a4c05c3869b5e27b5b93577c009702c544271cfa5760b3124fd7/.venv/.lockDEBUG Released lock at/Users/fatelei/.cache/uv/.lock` TRACE Streams::recv_eof TRACE Streams::recv_eof failed to init environment@dosubot[bot] commented on GitHub (Jan 13, 2026):
The Slack bot plugin installation fails because its requirements.txt pins werkzeug==3.1.5, but another dependency (likely dify_plugin==0.5.0) requires werkzeug>=3.0.3,<3.1.dev0, making the environment unsatisfiable details PR #2392.
You can try these workarounds:
Manual changes may cause breakage or be lost on plugin updates, so test in a non-production environment first. Each plugin runs in its own isolated virtual environment, so resolve conflicts within that environment reference. Monitor the repository for future updates that may address this more robustly.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other