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

[PR #318] [MERGED] fix: support serverless plugin management with execution timeout #444

New Issue
Closed
opened 2026-02-16 01:15:58 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 01:15:58 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugin-daemon/pull/318
Author: @Yeuoly
Created: 5/30/2025
Status: ✅ Merged
Merged: 5/30/2025
Merged by: @Yeuoly

Base: main ← Head: fix/hardcoded-serverless-runtime-timeout

📝 Commits (1)

  • 3ed5ef8 fix: support serverless plugin management with execution timeout

📊 Changes

8 files changed (+41 additions, -32 deletions)

View changed files

📝 internal/core/plugin_manager/manager.go (+3 -0)
📝 internal/core/plugin_manager/serverless.go (+5 -4)
📝 internal/core/plugin_manager/serverless_runtime/environment.go (+2 -2)
📝 internal/core/plugin_manager/serverless_runtime/io.go (+17 -22)
📝 internal/core/plugin_manager/serverless_runtime/run.go (+3 -3)
📝 internal/core/plugin_manager/serverless_runtime/type.go (+3 -1)
📝 internal/utils/http_requests/http_options.go (+5 -0)
📝 internal/utils/http_requests/http_request.go (+3 -0)

📄 Description

  • Added pluginMaxExecutionTimeout to PluginManager for configurable execution limits.
  • Updated ServerlessPluginRuntime to utilize the new timeout setting in HTTP requests.
  • Refactored AWSPluginRuntime references to ServerlessPluginRuntime for consistency across the codebase.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugin-daemon/pull/318 **Author:** [@Yeuoly](https://github.com/Yeuoly) **Created:** 5/30/2025 **Status:** ✅ Merged **Merged:** 5/30/2025 **Merged by:** [@Yeuoly](https://github.com/Yeuoly) **Base:** `main` ← **Head:** `fix/hardcoded-serverless-runtime-timeout` --- ### 📝 Commits (1) - [`3ed5ef8`](https://github.com/langgenius/dify-plugin-daemon/commit/3ed5ef823570ca56ba883fba4aa18c600bff644c) fix: support serverless plugin management with execution timeout ### 📊 Changes **8 files changed** (+41 additions, -32 deletions) <details> <summary>View changed files</summary> 📝 `internal/core/plugin_manager/manager.go` (+3 -0) 📝 `internal/core/plugin_manager/serverless.go` (+5 -4) 📝 `internal/core/plugin_manager/serverless_runtime/environment.go` (+2 -2) 📝 `internal/core/plugin_manager/serverless_runtime/io.go` (+17 -22) 📝 `internal/core/plugin_manager/serverless_runtime/run.go` (+3 -3) 📝 `internal/core/plugin_manager/serverless_runtime/type.go` (+3 -1) 📝 `internal/utils/http_requests/http_options.go` (+5 -0) 📝 `internal/utils/http_requests/http_request.go` (+3 -0) </details> ### 📄 Description - Added `pluginMaxExecutionTimeout` to `PluginManager` for configurable execution limits. - Updated `ServerlessPluginRuntime` to utilize the new timeout setting in HTTP requests. - Refactored AWSPluginRuntime references to ServerlessPluginRuntime for consistency across the codebase. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 01:15:58 -05:00
yindo closed this issue 2026-02-16 01:15:58 -05:00
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 pull-request
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#444
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?