langgenius/dify-plugin-daemon
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-daemon.git synced 2026-07-21 17:25:23 -04:00
Code Issues 111 Packages Projects Releases 10 Wiki Activity

OpenAI and Speech-to-Text blocks hang when running STT workflow in dify-plugin-daemon on Kubernetes #95

New Issue
Open
opened 2026-02-16 00:19:45 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 00:19:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @hiro-o918 on GitHub (Apr 21, 2025).

Environment

  • Deployment: Kubernetes
  • Runtime Version: 0.0.7-local

Problem Description

We are encountering an issue where OpenAI blocks become unresponsive when a workflow involving the Speech-to-Text (STT) block is executed. Additionally, the workflow containing the STT block itself hangs indefinitely and does not return any results.

Observations

  • When the STT workflow is running, all concurrent or subsequent OpenAI block executions appear to be blocked.
  • Pod metrics indicate that the relevant process within the dify-plugin-daemon pod consumes 1 full CPU core during this state.
  • This behavior leads us to suspect that the daemon might be single-threaded or facing a bottleneck related to concurrent processing, particularly when handling STT operations.

Questions

  1. Is there a known issue or potential reason why the Speech-to-Text (STT) block would cause other OpenAI blocks to hang and fail to complete itself?
  2. What are the recommended practices or configurations for deploying and managing the dify-plugin-daemon on Kubernetes, potentially including considerations for scaling or concurrency to handle workloads like STT?

Thank you for your support.

Originally created by @hiro-o918 on GitHub (Apr 21, 2025). ## Environment * **Deployment:** Kubernetes * **Runtime Version:** `0.0.7-local` ## Problem Description We are encountering an issue where `OpenAI` blocks become unresponsive when a workflow involving the Speech-to-Text (`STT`) block is executed. Additionally, the workflow containing the `STT` block itself hangs indefinitely and does not return any results. ## Observations * When the `STT` workflow is running, all concurrent or subsequent `OpenAI` block executions appear to be blocked. * Pod metrics indicate that the relevant process within the `dify-plugin-daemon` pod consumes 1 full CPU core during this state. * This behavior leads us to suspect that the daemon might be single-threaded or facing a bottleneck related to concurrent processing, particularly when handling `STT` operations. ## Questions 1. Is there a known issue or potential reason why the Speech-to-Text (`STT`) block would cause other `OpenAI` blocks to hang and fail to complete itself? 2. What are the recommended practices or configurations for deploying and managing the `dify-plugin-daemon` on Kubernetes, potentially including considerations for scaling or concurrency to handle workloads like `STT`? Thank you for your support.
yindo added the plugin-daemon label 2026-02-16 00:19:45 -05:00
yindo commented 2026-02-16 00:19:46 -05:00
Author
Owner
Copy Link
Copy Source

@hiro-o918 commented on GitHub (Apr 21, 2025):

This is probably an issue of https://github.com/langgenius/dify-plugin-sdks

@hiro-o918 commented on GitHub (Apr 21, 2025): This is probably an issue of https://github.com/langgenius/dify-plugin-sdks
yindo commented 2026-02-16 00:19:46 -05:00
Author
Owner
Copy Link
Copy Source

@Yeuoly commented on GitHub (Apr 22, 2025):

What's the size of your STT file?

@Yeuoly commented on GitHub (Apr 22, 2025): What's the size of your STT file?
yindo commented 2026-02-16 00:19:47 -05:00
Author
Owner
Copy Link
Copy Source

@hiro-o918 commented on GitHub (Apr 22, 2025):

@Yeuoly
Thank you for your response.
It is mp3 audio data with 7MB

@hiro-o918 commented on GitHub (Apr 22, 2025): @Yeuoly Thank you for your response. It is mp3 audio data with 7MB
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Windows
bug
cmd
documentation
enhancement
go
good first issue
plugin-daemon
pull-request
Mirrored from GitHub Pull Request
 question
No Label plugin-daemon
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-plugin-daemon#95
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?