mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
Add rerank model meet error #528
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 @Jimmy-L99 on GitHub (Aug 6, 2025).
Self Checks
Dify version
dify v1.7.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
The rerank model was deploy by sglang.
When I add rerank model, the error show:
list indices must be integers or slices, not strThen I
docker logs -f docker-api-1meet the error as follow:But if I use vLLM to deploy rerank model, it can be add in dify normally. Why?
What should I do to fix this error?
✔️ Expected Behavior
Can normally add the rerank model.
❌ Actual Behavior
No response
@dosubot[bot] commented on GitHub (Aug 6, 2025):
The error happens because Dify expects the plugin daemon to return error responses as JSON objects (dicts), but sometimes it gets a list instead, which breaks the error handler and causes the "list indices must be integers or slices, not str" message. This is both a robustness bug in Dify and a plugin-side bug with the response format [source].
To fix or work around this:
top_n) are set and valid. Missing or misconfigured fields (liketop_nbeingNone) are a common cause [source].This issue is known and not fully resolved upstream, so these steps should help you work around it for now [source].
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

@Jimmy-L99 commented on GitHub (Aug 6, 2025):
@dosu I deployed
Difyusing Docker Compose. Is this a bug in the Dify version or is there a problem with my configuration?@dosubot[bot] commented on GitHub (Aug 23, 2025):
Hi, @Jimmy-L99. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
top_nfield), ensuring plugin daemon error responses are JSON objects, and adding type checks in Dify's error handler.What's Next:
Thank you for your understanding and contribution!