langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

[tools] Dependency on non-existing requests>=2.32.7 #955

New Issue
Open
opened 2026-02-16 10:21:07 -05:00 by yindo · 8 comments
yindo commented 2026-02-16 10:21:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @kurokobo on GitHub (Jan 28, 2026).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues Dify issues & Dify Official Plugins, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.11.4

Plugin version

N/A

Cloud or Self Hosted

Cloud

Steps to reproduce

  1. Try packaging one of the following plugins from the source code (by plugin package command), and try installing it on the self-hosted environment.
    • Outlook
    • BitBucket
    • Dropbox
    • Minimax TTS

✔️ Error log

Dependencies cannot be solved due to non-existing requests

  × No solution found when resolving dependencies:
  ╰─▶ Because only the following versions of dify-plugin are available:
          dify-plugin<=0.4.2
          dify-plugin==0.4.3
          dify-plugin==0.4.4
          dify-plugin==0.4.5
          dify-plugin>=0.5.0
      and dify-plugin>=0.4.2,<=0.4.5 depends on requests>=2.32.3, we can
      conclude that dify-plugin>=0.4.2,<0.5.0 depends on requests>=2.32.3.
      And because only requests<=2.32.5 is available, we can conclude that
      dify-plugin>=0.4.2,<0.5.0 depends on requests>=2.32.3.
      And because you require dify-plugin>=0.4.2,<0.5.0 and requests>=2.32.7,
      we can conclude that your requirements are unsatisfiable.

      hint: Pre-releases are available for `dify-plugin` in the requested
      range (e.g., 0.4.5b2), but pre-releases weren't enabled (try:
      `--prerelease=allow`)

      hint: `requests` was requested with a pre-release marker (e.g.,
      requests>=2.32.7,<2.33.dev0), but pre-releases weren't enabled (try:
      `--prerelease=allow`)
Originally created by @kurokobo on GitHub (Jan 28, 2026). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.11.4 ### Plugin version N/A ### Cloud or Self Hosted Cloud ### Steps to reproduce 1. Try packaging one of the following plugins from the source code (by `plugin package` command), and try installing it on the self-hosted environment. - Outlook - BitBucket - Dropbox - Minimax TTS ### ✔️ Error log Dependencies cannot be solved due to non-existing `requests` ```bash  × No solution found when resolving dependencies: ╰─▶ Because only the following versions of dify-plugin are available: dify-plugin<=0.4.2 dify-plugin==0.4.3 dify-plugin==0.4.4 dify-plugin==0.4.5 dify-plugin>=0.5.0 and dify-plugin>=0.4.2,<=0.4.5 depends on requests>=2.32.3, we can conclude that dify-plugin>=0.4.2,<0.5.0 depends on requests>=2.32.3. And because only requests<=2.32.5 is available, we can conclude that dify-plugin>=0.4.2,<0.5.0 depends on requests>=2.32.3. And because you require dify-plugin>=0.4.2,<0.5.0 and requests>=2.32.7, we can conclude that your requirements are unsatisfiable. hint: Pre-releases are available for `dify-plugin` in the requested range (e.g., 0.4.5b2), but pre-releases weren't enabled (try: `--prerelease=allow`) hint: `requests` was requested with a pre-release marker (e.g., requests>=2.32.7,<2.33.dev0), but pre-releases weren't enabled (try: `--prerelease=allow`) ```
yindo added the bug label 2026-02-16 10:21:07 -05:00
yindo commented 2026-02-16 10:21:07 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 28, 2026):

The dependency conflict happens because plugins like Outlook, Dropbox, and Minimax TTS require requests>=2.32.7, but only requests<=2.32.5 is available in your environment, making the requirements unsatisfiable. This strict pin is present in their requirements.txt and pyproject.toml files, and is compounded by the fact that dify-plugin itself also manages a requests dependency in a similar range, leading to a deadlock when the solver can't find a compatible version (example).

Recent updates in the repository (see PR #2440) have started loosening or removing these strict requests version pins from several plugins, which should help resolve this issue as new plugin versions are released. Until those updates reach all plugins, you have a few workarounds:

  • If you control the plugin files, edit their requirements.txt or pyproject.toml to relax the requests version constraint to something like requests>=2.32.3,<2.33.0 or match the version actually available in your environment.
  • If the error message suggests pre-releases are available, you can try enabling pre-release installs by manually running pip install --pre requests (or the relevant dependency) inside the plugin's virtual environment (workaround details).
  • For offline or air-gapped installs, use the dify-plugin-repackaging tool to bundle the plugin with all required dependencies, ensuring the correct requests version is included (reference).
  • Upgrading to the latest plugin versions as they are released should eventually resolve these conflicts, since maintainers are actively removing strict or pre-release dependency pins (PR #2440).

If you get stuck in a failed install state, clear plugin install tasks and plugin data, then restart the plugin daemon before retrying (more tips).

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 28, 2026): <!-- Answer --> The dependency conflict happens because plugins like Outlook, Dropbox, and Minimax TTS require `requests>=2.32.7`, but only `requests<=2.32.5` is available in your environment, making the requirements unsatisfiable. This strict pin is present in their `requirements.txt` and `pyproject.toml` files, and is compounded by the fact that `dify-plugin` itself also manages a `requests` dependency in a similar range, leading to a deadlock when the solver can't find a compatible version ([example](https://github.com/langgenius/dify-official-plugins/blob/a74ee6819e59367091442dc1abc4f275e5bdec92/tools/outlook/requirements.txt#L1-L2)). Recent updates in the repository (see PR [#2440](https://github.com/langgenius/dify-official-plugins/pull/2440)) have started loosening or removing these strict `requests` version pins from several plugins, which should help resolve this issue as new plugin versions are released. Until those updates reach all plugins, you have a few workarounds: - If you control the plugin files, edit their `requirements.txt` or `pyproject.toml` to relax the `requests` version constraint to something like `requests>=2.32.3,<2.33.0` or match the version actually available in your environment. - If the error message suggests pre-releases are available, you can try enabling pre-release installs by manually running `pip install --pre requests` (or the relevant dependency) inside the plugin's virtual environment ([workaround details](https://github.com/langgenius/dify/issues/30928)). - For offline or air-gapped installs, use the [dify-plugin-repackaging tool](https://github.com/junjiem/dify-plugin-repackaging) to bundle the plugin with all required dependencies, ensuring the correct `requests` version is included ([reference](https://github.com/langgenius/dify/issues/20424)). - Upgrading to the latest plugin versions as they are released should eventually resolve these conflicts, since maintainers are actively removing strict or pre-release dependency pins ([PR #2440](https://github.com/langgenius/dify-official-plugins/pull/2440)). If you get stuck in a failed install state, clear plugin install tasks and plugin data, then restart the plugin daemon before retrying ([more tips](https://github.com/langgenius/dify/issues/31046)). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/03b44296-f4d7-4601-b1f0-7c674b19fa77?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/03b44296-f4d7-4601-b1f0-7c674b19fa77?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/03b44296-f4d7-4601-b1f0-7c674b19fa77?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/03b44296-f4d7-4601-b1f0-7c674b19fa77?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/03b44296-f4d7-4601-b1f0-7c674b19fa77?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/03b44296-f4d7-4601-b1f0-7c674b19fa77?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/03b44296-f4d7-4601-b1f0-7c674b19fa77?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20dependency%20conflict%20happens%20because%20plugins%20like%20Outlook%2C%20Dropbox%2C%20and%20Minimax%20TTS%20require%20%60requests%3E%3D2.32.7%60%2C%20but%20only%20%60requests%3C%3D2.32.5%60%20is%20available%20in%20your%20environment%2C%20making%20the%20requirements%20unsatisfiable.%20This%20strict%20pin%20is%20present%20in%20their%20%60requirements.txt%60%20and%20%60pyproject.toml%60%20files%2C%20and%20is%20compounded%20by%20the%20fact%20that%20%60dify-plugin%60%20itself%20also%20manages%20a%20%60requests%60%20dependency%20in%20a%20similar%20range%2C%20leading%20to%20a%20deadlock%20when%20the%20solver%20can%27t%20find%20a%20compatible%20version%C2%A0%28%5Bexample%5D%28https%3A//github.com/langgenius/dify-official-plugins/blob/a74ee6819e59367091442dc1abc4f275e5bdec92/tools/outlook/requirements.txt%23L1-L2%29%29.%0A%0ARecent%20updates%20in%20the%20repository%20%28see%20PR%C2%A0%5B%232440%5D%28https%3A//github.com/langgenius/dify-official-plugins/pull/2440%29%29%20have%20started%20loosening%20or%20removing%20these%20strict%20%60requests%60%20version%20pins%20from%20several%20plugins%2C%20which%20should%20help%20resolve%20this%20issue%20as%20new%20plugin%20versions%20are%20released.%20Until%20those%20updates%20reach%20all%20plugins%2C%20you%20have%20a%20few%20workarounds%3A%0A%0A-%20If%20you%20control%20the%20plugin%20files%2C%20edit%20their%20%60requirements.txt%60%20or%20%60pyproject.toml%60%20to%20relax%20the%20%60requests%60%20version%20constraint%20to%20something%20like%20%60requests%3E%3D2.32.3%2C%3C2.33.0%60%20or%20match%20the%20version%20actually%20available%20in%20your%20environment.%0A-%20If%20the%20error%20message%20suggests%20pre-releases%20are%20available%2C%20you%20can%20try%20enabling%20pre-release%20installs%20by%20manually%20running%20%60pip%20install%20--pre%20requests%60%20%28or%20the%20relevant%20dependency%29%20inside%20the%20plugin%27s%20virtual%20environment%C2%A0%28%5Bworkaround%20details%5D%28https%3A//github.com/langgenius/dify/issues/30928%29%29.%0A-%20For%20offline%20or%20air-gapped%20installs%2C%20use%20the%20%5Bdify-plugin-repackaging%20tool%5D%28https%3A//github.com/junjiem/dify-plugin-repackaging%29%20to%20bundle%20the%20plugin%20with%20all%20required%20dependencies%2C%20ensuring%20the%20correct%20%60requests%60%20version%20is%20included%C2%A0%28%5Breference%5D%28https%3A//github.com/langgenius/dify/issues/20424%29%29.%0A-%20Upgrading%20to%20the%20latest%20plugin%20versions%20as%20they%20are%20released%20should%20eventually%20resolve%20these%20conflicts%2C%20since%20maintainers%20are%20actively%20removing%20strict%20or%20pre-release%20dependency%20pins%C2%A0%28%5BPR%20%232440%5D%28https%3A//github.com/langgenius/dify-official-plugins/pull/2440%29%29.%0A%0AIf%20you%20get%20stuck%20in%20a%20failed%20install%20state%2C%20clear%20plugin%20install%20tasks%20and%20plugin%20data%2C%20then%20restart%20the%20plugin%20daemon%20before%20retrying%C2%A0%28%5Bmore%20tips%5D%28https%3A//github.com/langgenius/dify/issues/31046%29%29.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/2510)
yindo commented 2026-02-16 10:21:07 -05:00
Author
Owner
Copy Link
Copy Source

@kurokobo commented on GitHub (Jan 28, 2026):

@crazywoola
Hi, I noticed that you bumped the requests version to 2.32.7 or higher in https://github.com/langgenius/dify-official-plugins/pull/1849, but there is no such version available on PyPI.
The latest requests is 2.32.5: https://pypi.org/project/requests/#history

So perhaps following tools cannot be installed.

$ grep -R --include="*.txt" --include="*.toml" 2.32.7 .
./tools/bitbucket/requirements.txt:requests==2.32.7
./tools/dropbox/pyproject.toml:    "requests~=2.32.7",
./tools/dropbox/requirements.txt:requests~=2.32.7
./tools/minimax_tts/pyproject.toml:    "requests>=2.32.7",
./tools/minimax_tts/requirements.txt:requests>=2.32.7
@kurokobo commented on GitHub (Jan 28, 2026): @crazywoola Hi, I noticed that you bumped the `requests` version to `2.32.7` or higher in https://github.com/langgenius/dify-official-plugins/pull/1849, but there is no such version available on PyPI. The latest `requests` is `2.32.5`: https://pypi.org/project/requests/#history So perhaps following tools cannot be installed. ```bash $ grep -R --include="*.txt" --include="*.toml" 2.32.7 . ./tools/bitbucket/requirements.txt:requests==2.32.7 ./tools/dropbox/pyproject.toml: "requests~=2.32.7", ./tools/dropbox/requirements.txt:requests~=2.32.7 ./tools/minimax_tts/pyproject.toml: "requests>=2.32.7", ./tools/minimax_tts/requirements.txt:requests>=2.32.7 ```
yindo commented 2026-02-16 10:21:07 -05:00
Author
Owner
Copy Link
Copy Source

@kurokobo commented on GitHub (Jan 28, 2026):

For now, I've updated Outlook plugin to use the latest version 2.32.5 in my PR https://github.com/langgenius/dify-official-plugins/pull/2509. What do you think we should do about the other tools?

Also, I'm not sure if this was intentional, but your previous PR didn't change the plugin version, so it looks like the problematic requirements.txt hasn't been released to the marketplace.

@kurokobo commented on GitHub (Jan 28, 2026): For now, I've updated Outlook plugin to use the latest version 2.32.5 in my PR https://github.com/langgenius/dify-official-plugins/pull/2509. What do you think we should do about the other tools? Also, I'm not sure if this was intentional, but your previous PR didn't change the plugin version, so it looks like the problematic requirements.txt hasn't been released to the marketplace.
yindo commented 2026-02-16 10:21:07 -05:00
Author
Owner
Copy Link
Copy Source

@kurokobo commented on GitHub (Jan 28, 2026):

Since the dify_plugin module already depends on requirements, it might not be necessary to include requests in each plugin’s requirements.txt. Removing all of them could be another solution.

@kurokobo commented on GitHub (Jan 28, 2026): Since the dify_plugin module already depends on requirements, it might not be necessary to include requests in each plugin’s requirements.txt. Removing all of them could be another solution.
yindo commented 2026-02-16 10:21:07 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 3, 2026):

Hi @kurokobo, thanks for opening this issue.

Why this is being closed

Dify issue tracking requires English-only issue title and description for consistent collaboration.

Next steps

Please open a new issue in English and include clear details so maintainers can help efficiently.

Thanks for understanding and for your support.

@crazywoola commented on GitHub (Feb 3, 2026): Hi @kurokobo, thanks for opening this issue. ### Why this is being closed Dify issue tracking requires English-only issue title and description for consistent collaboration. ### Next steps Please open a new issue in English and include clear details so maintainers can help efficiently. Thanks for understanding and for your support.
yindo commented 2026-02-16 10:21:07 -05:00
Author
Owner
Copy Link
Copy Source

@kurokobo commented on GitHub (Feb 3, 2026):

@crazywoola
Is this closure intentional? I'm fine with closing it, but the reason "because it's not in English" is clearly incorrect. I have only used English in this issue.

@kurokobo commented on GitHub (Feb 3, 2026): @crazywoola Is this closure intentional? I'm fine with closing it, but the reason "because it's not in English" is clearly incorrect. I have only used English in this issue.
yindo commented 2026-02-16 10:21:07 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 3, 2026):

@kurokobo Sorry, I am testing some review bot at this moment. :(

@crazywoola commented on GitHub (Feb 3, 2026): @kurokobo Sorry, I am testing some review bot at this moment. :(
yindo commented 2026-02-16 10:21:07 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 3, 2026):

@kurokobo It should work as expected now :)

@crazywoola commented on GitHub (Feb 3, 2026): @kurokobo It should work as expected now :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#955
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?