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

[TONGYI]After upgrading Dify to version 1.11.0, the Tongyi plugin became unusable and cannot be reinstalled after uninstallation. #872

New Issue
Closed
opened 2026-02-16 10:20:48 -05:00 by yindo · 9 comments
yindo commented 2026-02-16 10:20:48 -05:00
Owner
Copy Link
Copy Source

Originally created by @bud-thomas on GitHub (Dec 12, 2025).

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

Plugin version

0.1.8

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I upgraded Dify from version 1.9.2 to 1.11.0.
Then I discovered that the Dify workflow was malfunctioning. While debugging, I saw the Tongyi plugin throwing an error: error: slice indices must be integers or None or have an index method. like this: 29453.So I uninstalled the Tongyi plugin, but now I can't reinstall it.

Image

✔️ Error log

plugin_daemon-1     | 2025/12/12 07:08:16 /app/internal/db/executor.go:259 record not found

api-1               | 2025-12-12 15:09:19.090 ERROR [Dummy-44] [base.py:277]  - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\\"error_type\\":\\"unmarshal_error\\",\\"message\\":\\"unmarshal json failed: use_template enable_thinking not found\\"}","error_type":"PluginInvokeError","args":null}', 'data': None}
api-1               | 2025-12-12 15:09:19.091 WARNING [Dummy-44] [provider_configuration.py:1740]  - get custom model schema failed, req_id: f1333f0f4f PluginInvokeError: {"error_type":"unmarshal_error","message":"unmarshal json failed: use_template enable_thinking not found"}
Originally created by @bud-thomas on GitHub (Dec 12, 2025). ### 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.0 ### Plugin version 0.1.8 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I upgraded Dify from version 1.9.2 to 1.11.0. Then I discovered that the Dify workflow was malfunctioning. While debugging, I saw the Tongyi plugin throwing an error: `error: slice indices must be integers or None or have an index method.` like this: [29453](https://github.com/langgenius/dify/issues/29453).So I uninstalled the Tongyi plugin, but now I can't reinstall it. <img width="436" height="104" alt="Image" src="https://github.com/user-attachments/assets/fb49b854-1872-433a-87b5-0e0f05653e40" /> ### ✔️ Error log ``` plugin_daemon-1 | 2025/12/12 07:08:16 /app/internal/db/executor.go:259 record not found api-1 | 2025-12-12 15:09:19.090 ERROR [Dummy-44] [base.py:277] - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\\"error_type\\":\\"unmarshal_error\\",\\"message\\":\\"unmarshal json failed: use_template enable_thinking not found\\"}","error_type":"PluginInvokeError","args":null}', 'data': None} api-1 | 2025-12-12 15:09:19.091 WARNING [Dummy-44] [provider_configuration.py:1740] - get custom model schema failed, req_id: f1333f0f4f PluginInvokeError: {"error_type":"unmarshal_error","message":"unmarshal json failed: use_template enable_thinking not found"} ```
yindo added the bug label 2026-02-16 10:20:48 -05:00
yindo closed this issue 2026-02-16 10:20:48 -05:00
yindo commented 2026-02-16 10:20:48 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 12, 2025):

Dify 1.11.0 introduced significant changes to the plugin system, including new required fields in plugin configuration schemas (like use_template, template, and scope). These changes can break compatibility with plugins built for earlier versions, such as the Tongyi plugin v0.1.8. The error unmarshal json failed: use_template enable_thinking not found means Dify is expecting configuration fields that the Tongyi plugin does not provide, leading to installation and runtime failures. The slice indices must be integers error is also a symptom of schema mismatches introduced by these updates [source] [source].

Currently, there are no merged fixes in the official plugins repo addressing this compatibility issue. The Tongyi plugin manifest and provider YAML do not define the new required fields, nor do they mention compatibility with Dify 1.11.0 [source] [source].

To resolve this, you will need to wait for an updated version of the Tongyi plugin that explicitly supports Dify 1.11.0's new schema, or manually patch the plugin's configuration to include the required fields. If you need to urgently restore functionality, consider rolling back to Dify 1.9.x until a compatible plugin release is available.

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 (Dec 12, 2025): <!-- Answer --> Dify 1.11.0 introduced significant changes to the plugin system, including new required fields in plugin configuration schemas (like `use_template`, `template`, and `scope`). These changes can break compatibility with plugins built for earlier versions, such as the Tongyi plugin v0.1.8. The error `unmarshal json failed: use_template enable_thinking not found` means Dify is expecting configuration fields that the Tongyi plugin does not provide, leading to installation and runtime failures. The `slice indices must be integers` error is also a symptom of schema mismatches introduced by these updates [[source]](https://github.com/langgenius/dify/pull/25283) [[source]](https://github.com/langgenius/dify/blob/e244856ef1b2f2f3bb230e76ea04523839b5d802/api/core/model_runtime/entities/model_entities.py#L168-L216). Currently, there are no merged fixes in the official plugins repo addressing this compatibility issue. The Tongyi plugin manifest and provider YAML do not define the new required fields, nor do they mention compatibility with Dify 1.11.0 [[source]](https://github.com/langgenius/dify-official-plugins/blob/9ab968878ff82aa2c2cec522e4fbf925594fb4ff/models/tongyi/manifest.yaml#L1-L30) [[source]](https://github.com/langgenius/dify-official-plugins/blob/9ab968878ff82aa2c2cec522e4fbf925594fb4ff/models/tongyi/provider/tongyi.yaml#L28-L132). To resolve this, you will need to wait for an updated version of the Tongyi plugin that explicitly supports Dify 1.11.0's new schema, or manually patch the plugin's configuration to include the required fields. If you need to urgently restore functionality, consider rolling back to Dify 1.9.x until a compatible plugin release is available. <!-- 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/1f67a3f8-7dff-415b-9af7-8abef3734d33?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1f67a3f8-7dff-415b-9af7-8abef3734d33?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1f67a3f8-7dff-415b-9af7-8abef3734d33?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1f67a3f8-7dff-415b-9af7-8abef3734d33?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1f67a3f8-7dff-415b-9af7-8abef3734d33?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1f67a3f8-7dff-415b-9af7-8abef3734d33?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1f67a3f8-7dff-415b-9af7-8abef3734d33?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Dify%201.11.0%20introduced%20significant%20changes%20to%20the%20plugin%20system%2C%20including%20new%20required%20fields%20in%20plugin%20configuration%20schemas%20%28like%20%60use_template%60%2C%20%60template%60%2C%20and%20%60scope%60%29.%20These%20changes%20can%20break%20compatibility%20with%20plugins%20built%20for%20earlier%20versions%2C%20such%20as%20the%20Tongyi%20plugin%20v0.1.8.%20The%20error%20%60unmarshal%20json%20failed%3A%20use_template%20enable_thinking%20not%20found%60%20means%20Dify%20is%20expecting%20configuration%20fields%20that%20the%20Tongyi%20plugin%20does%20not%20provide%2C%20leading%20to%20installation%20and%20runtime%20failures.%20The%20%60slice%20indices%20must%20be%20integers%60%20error%20is%20also%20a%20symptom%20of%20schema%20mismatches%20introduced%20by%20these%20updates%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify/pull/25283%29%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify/blob/e244856ef1b2f2f3bb230e76ea04523839b5d802/api/core/model_runtime/entities/model_entities.py%23L168-L216%29.%0A%0ACurrently%2C%20there%20are%20no%20merged%20fixes%20in%20the%20official%20plugins%20repo%20addressing%20this%20compatibility%20issue.%20The%20Tongyi%20plugin%20manifest%20and%20provider%20YAML%20do%20not%20define%20the%20new%20required%20fields%2C%20nor%20do%20they%20mention%20compatibility%20with%20Dify%201.11.0%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify-official-plugins/blob/9ab968878ff82aa2c2cec522e4fbf925594fb4ff/models/tongyi/manifest.yaml%23L1-L30%29%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify-official-plugins/blob/9ab968878ff82aa2c2cec522e4fbf925594fb4ff/models/tongyi/provider/tongyi.yaml%23L28-L132%29.%0A%0ATo%20resolve%20this%2C%20you%20will%20need%20to%20wait%20for%20an%20updated%20version%20of%20the%20Tongyi%20plugin%20that%20explicitly%20supports%20Dify%201.11.0%27s%20new%20schema%2C%20or%20manually%20patch%20the%20plugin%27s%20configuration%20to%20include%20the%20required%20fields.%20If%20you%20need%20to%20urgently%20restore%20functionality%2C%20consider%20rolling%20back%20to%20Dify%201.9.x%20until%20a%20compatible%20plugin%20release%20is%20available.)&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/2245)
yindo commented 2026-02-16 10:20:48 -05:00
Author
Owner
Copy Link
Copy Source

@Once2012 commented on GitHub (Dec 14, 2025):

I encountered a similar problem. After upgrading Dify to version 1.11.1, all processes involving the qwen3 model started to report errors. Even after reverting to version 1.10.1 and fixing it, the problem persisted. My previous Tongyi 0.1.13 was upgraded from Dify 1.9.1 to Dify 1.10.1.fix to fix the vulnerabilities. There were no problems with this upgrade. But I reinstalled version 1.10.1.fix and attempted to downgrade the Tongyi plugin from 0.1.18 to 0.1.13, but failed to do so no matter what.

@Once2012 commented on GitHub (Dec 14, 2025): I encountered a similar problem. After upgrading Dify to version 1.11.1, all processes involving the qwen3 model started to report errors. Even after reverting to version 1.10.1 and fixing it, the problem persisted. My previous Tongyi 0.1.13 was upgraded from Dify 1.9.1 to Dify 1.10.1.fix to fix the vulnerabilities. There were no problems with this upgrade. But I reinstalled version 1.10.1.fix and attempted to downgrade the Tongyi plugin from 0.1.18 to 0.1.13, but failed to do so no matter what.
yindo commented 2026-02-16 10:20:48 -05:00
Author
Owner
Copy Link
Copy Source

@Once2012 commented on GitHub (Dec 14, 2025):

Reached maximum retries (3) for URL https://marketplace.dify.ai/api/v1/plugins/download?unique_identifier=langgenius/tongyi:0.1.3@08f25a10c0617a3512fac091a0f0d894925357e965efe40fdf95cb48e09b62d1

The http response:
{"code":-1,"data":null,"msg":"plugin package not found"}

@Once2012 commented on GitHub (Dec 14, 2025): Reached maximum retries (3) for URL https://marketplace.dify.ai/api/v1/plugins/download?unique_identifier=langgenius/tongyi:0.1.3@08f25a10c0617a3512fac091a0f0d894925357e965efe40fdf95cb48e09b62d1 The http response: {"code":-1,"data":null,"msg":"plugin package not found"}
yindo commented 2026-02-16 10:20:49 -05:00
Author
Owner
Copy Link
Copy Source

@bud-thomas commented on GitHub (Dec 14, 2025):

@dosu

failed to launch plugin: failed to install dependencies: failed to install dependencies: signal: killed, output: DEBUG uv 0.9.17 TRACE Checking lock for `/root/.cache/uv` at `/root/.cache/uv/.lock` DEBUG Acquired shared lock for `/root/.cache/uv` DEBUG Searching for default Python interpreter in virtual environments TRACE Found cached interpreter info for Python 3.12.3, skipping query of: .venv/bin/python3 DEBUG Found `cpython-3.12.3-linux-x86_64-gnu` at `/app/storage/cwd/langgenius/tongyi-0.1.8@65112e77031...1731886 TRACE send_data; sz=2795; window=4465780; available=5242880 TRACE send_data; sz=2795; window=1731886; available=2097152 TRACE transition_after; stream=StreamId(1); state=HalfClosedLocal(Streaming); is_closed=false; pending_send_empty=true; buffered_send_data=0; num_recv=0; num_send=2 TRACE poll TRACE poll_complete TRACE schedule_pending_open TRACE flushing buffer TRACE release_capacity; size=2795 TRACE release_connection_capacity; size=2795, connection in_flight_data=2795 failed to init environment
@bud-thomas commented on GitHub (Dec 14, 2025): [@dosu](https://go.dosu.dev/dosubot) ``` failed to launch plugin: failed to install dependencies: failed to install dependencies: signal: killed, output: DEBUG uv 0.9.17 TRACE Checking lock for `/root/.cache/uv` at `/root/.cache/uv/.lock` DEBUG Acquired shared lock for `/root/.cache/uv` DEBUG Searching for default Python interpreter in virtual environments TRACE Found cached interpreter info for Python 3.12.3, skipping query of: .venv/bin/python3 DEBUG Found `cpython-3.12.3-linux-x86_64-gnu` at `/app/storage/cwd/langgenius/tongyi-0.1.8@65112e77031...1731886 TRACE send_data; sz=2795; window=4465780; available=5242880 TRACE send_data; sz=2795; window=1731886; available=2097152 TRACE transition_after; stream=StreamId(1); state=HalfClosedLocal(Streaming); is_closed=false; pending_send_empty=true; buffered_send_data=0; num_recv=0; num_send=2 TRACE poll TRACE poll_complete TRACE schedule_pending_open TRACE flushing buffer TRACE release_capacity; size=2795 TRACE release_connection_capacity; size=2795, connection in_flight_data=2795 failed to init environment ```
yindo commented 2026-02-16 10:20:49 -05:00
Author
Owner
Copy Link
Copy Source

@Stream29 commented on GitHub (Dec 15, 2025):

@Once2012 Can you try out the 0.1.9 version of tongyi plugin? It installed successfully on cloud.dify.ai.

@Stream29 commented on GitHub (Dec 15, 2025): @Once2012 Can you try out the `0.1.9` version of `tongyi` plugin? It installed successfully on `cloud.dify.ai`.
yindo commented 2026-02-16 10:20:49 -05:00
Author
Owner
Copy Link
Copy Source

@bud-thomas commented on GitHub (Dec 15, 2025):

你能试试插件版本吗？它成功安装在 。0.1.9``tongyi``cloud.dify.ai

It still seems to be the same issue.
Image

@bud-thomas commented on GitHub (Dec 15, 2025): > 你能试试插件版本吗？它成功安装在 。`0.1.9``tongyi``cloud.dify.ai` It still seems to be the same issue. <img width="470" height="175" alt="Image" src="https://github.com/user-attachments/assets/db2dbbe8-8eb5-4975-b510-2ed94a1cad2b" />
yindo commented 2026-02-16 10:20:49 -05:00
Author
Owner
Copy Link
Copy Source

@bud-thomas commented on GitHub (Dec 15, 2025):

I refreshed the page, and it looks like it's there now. The workflow is running properly as well, thanks.

@bud-thomas commented on GitHub (Dec 15, 2025): I refreshed the page, and it looks like it's there now. The workflow is running properly as well, thanks.
yindo commented 2026-02-16 10:20:49 -05:00
Author
Owner
Copy Link
Copy Source

@nadazero commented on GitHub (Dec 16, 2025):

如果是安装源的问题，请尝试修改.env中的PIP_MIRROR_URL=https://pypi.tuna.tsinghua.edu.cn/simple

@nadazero commented on GitHub (Dec 16, 2025): 如果是安装源的问题，请尝试修改.env中的PIP_MIRROR_URL=https://pypi.tuna.tsinghua.edu.cn/simple
yindo commented 2026-02-16 10:20:49 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi, @bud-thomas. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that after upgrading to Dify 1.11.0, the Tongyi plugin v0.1.8 stopped working due to missing required fields in the plugin schema.
  • The upgrade introduced breaking changes requiring updated plugin manifests.
  • No official fixes existed initially, with rollback or manual patching recommended.
  • Other users experienced similar issues, but Tongyi v0.1.9 was suggested as a fix.
  • You confirmed that Tongyi v0.1.9 started working after refreshing.

Next Steps:

  • Please confirm if this issue remains relevant with the latest versions of Dify and the Tongyi plugin.
  • If no further problems arise, I will automatically close this issue in 5 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 1, 2026): Hi, @bud-thomas. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that after upgrading to Dify 1.11.0, the Tongyi plugin v0.1.8 stopped working due to missing required fields in the plugin schema. - The upgrade introduced breaking changes requiring updated plugin manifests. - No official fixes existed initially, with rollback or manual patching recommended. - Other users experienced similar issues, but Tongyi v0.1.9 was suggested as a fix. - You confirmed that Tongyi v0.1.9 started working after refreshing. **Next Steps:** - Please confirm if this issue remains relevant with the latest versions of Dify and the Tongyi plugin. - If no further problems arise, I will automatically close this issue in 5 days. Thank you for your understanding and contribution!
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#872
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?