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

[ERROR]plugin langgenius/volcengine_maas:0.0.13 has an error on stdout: bufio.Scanner: token too long #304

New Issue
Closed
opened 2026-02-16 10:18:54 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 10:18:54 -05:00
Owner
Copy Link
Copy Source

Originally created by @liuyao02 on GitHub (May 22, 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 search for existing issues, 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.3.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

2025/05/22 03:45:05 stdio.go:166: [ERROR]plugin langgenius/volcengine_maas:0.0.13 has an error on stdout: bufio.Scanner: token too long
2025/05/22 03:45:05 run.go:132: [ERROR]plugin langgenius/volcengine_maas:0.0.13 exited with error: signal: killed

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

2025/05/22 03:45:05 stdio.go:166: [ERROR]plugin langgenius/volcengine_maas:0.0.13 has an error on stdout: bufio.Scanner: token too long
2025/05/22 03:45:05 run.go:132: [ERROR]plugin langgenius/volcengine_maas:0.0.13 exited with error: signal: killed

Image

Originally created by @liuyao02 on GitHub (May 22, 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 [search for existing issues](https://github.com/langgenius/dify/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.3.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 2025/05/22 03:45:05 stdio.go:166: [ERROR]plugin langgenius/volcengine_maas:0.0.13 has an error on stdout: bufio.Scanner: token too long 2025/05/22 03:45:05 run.go:132: [ERROR]plugin langgenius/volcengine_maas:0.0.13 exited with error: signal: killed ![Image](https://github.com/user-attachments/assets/f1770b86-e9eb-49c9-9c42-58daf672e7b3) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior 2025/05/22 03:45:05 stdio.go:166: [ERROR]plugin langgenius/volcengine_maas:0.0.13 has an error on stdout: bufio.Scanner: token too long 2025/05/22 03:45:05 run.go:132: [ERROR]plugin langgenius/volcengine_maas:0.0.13 exited with error: signal: killed ![Image](https://github.com/user-attachments/assets/f1770b86-e9eb-49c9-9c42-58daf672e7b3)
yindo closed this issue 2026-02-16 10:18:54 -05:00
yindo commented 2026-02-16 10:18:55 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 22, 2025):

The error [ERROR]plugin langgenius/volcengine_maas:0.0.13 has an error on stdout: bufio.Scanner: token too long in Dify 1.3.1 (self-hosted, Docker) is a known issue. It typically occurs when making workflow API requests with the doubao-1.5-vision-pro model using image and string parameters. The root cause is that the data being processed (often large images encoded as base64) exceeds the buffer size limit of Go's bufio.Scanner used internally by the plugin.

Solution:
Upgrading your Dify installation to version 1.4.0 or later resolves this error for the Volcengine plugin and the doubao-1.5-vision-pro model. This fix has been confirmed in recent issues and is the recommended approach for a permanent solution.
See details

Workarounds if you cannot upgrade immediately:

  • Reduce the size of images before uploading them, as large images are more likely to trigger this error.
  • Consider switching to a different specific model provider if possible, rather than using a generic or openai_api_compatible provider, which may also hit this limitation with large payloads.
    See related discussion

If you need more details about the plugin's error handling or want to review the relevant code, you can refer to the plugin's implementation, which raises a MaasError when requests fail, including detailed error information.

Upgrading is the most reliable fix for this issue. If you have any constraints preventing an upgrade, reducing image size or changing the provider may help as a temporary measure.

To continue talking to Dosu, mention @dosu-bot.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (May 22, 2025): <!-- Answer --> The error `[ERROR]plugin langgenius/volcengine_maas:0.0.13 has an error on stdout: bufio.Scanner: token too long` in Dify 1.3.1 (self-hosted, Docker) is a known issue. It typically occurs when making workflow API requests with the doubao-1.5-vision-pro model using image and string parameters. The root cause is that the data being processed (often large images encoded as base64) exceeds the buffer size limit of Go's `bufio.Scanner` used internally by the plugin. **Solution:** Upgrading your Dify installation to version 1.4.0 or later resolves this error for the Volcengine plugin and the doubao-1.5-vision-pro model. This fix has been confirmed in recent issues and is the recommended approach for a permanent solution. [See details](https://github.com/langgenius/dify-official-plugins/issues/1226) **Workarounds if you cannot upgrade immediately:** - Reduce the size of images before uploading them, as large images are more likely to trigger this error. - Consider switching to a different specific model provider if possible, rather than using a generic or openai_api_compatible provider, which may also hit this limitation with large payloads. [See related discussion](https://github.com/langgenius/dify/issues/18657) If you need more details about the plugin's error handling or want to review the relevant code, you can refer to the plugin's implementation, which raises a `MaasError` when requests fail, including detailed error information. Upgrading is the most reliable fix for this issue. If you have any constraints preventing an upgrade, reducing image size or changing the provider may help as a temporary measure. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://go.dosu.dev/dosubot), mention @dosu-bot.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/037551cd-11d3-41d0-a16b-6acccc003384?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/037551cd-11d3-41d0-a16b-6acccc003384?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/037551cd-11d3-41d0-a16b-6acccc003384?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/037551cd-11d3-41d0-a16b-6acccc003384?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/037551cd-11d3-41d0-a16b-6acccc003384?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/037551cd-11d3-41d0-a16b-6acccc003384?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/037551cd-11d3-41d0-a16b-6acccc003384?feedback_type=other)</sup>
yindo commented 2026-02-16 10:18:55 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (May 22, 2025):

Duplicated https://github.com/langgenius/dify-official-plugins/issues/1226

Please read the check list first:

@crazywoola commented on GitHub (May 22, 2025): Duplicated https://github.com/langgenius/dify-official-plugins/issues/1226 Please read the check list first: - I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones.
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
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#304
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?