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

[PR #1309] [MERGED] fix: gpustack image tool compatible url path #1827

New Issue
Closed
opened 2026-02-16 10:24:06 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 10:24:06 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-official-plugins/pull/1309
Author: @alexcodelf
Created: 7/19/2025
Status: ✅ Merged
Merged: 7/24/2025
Merged by: @crazywoola

Base: main ← Head: fix/gpustack-tools

📝 Commits (1)

  • a8e12f3 fix: gpustack image tool compatible url path

📊 Changes

4 files changed (+6 additions, -9 deletions)

View changed files

📝 tools/gpustack/manifest.yaml (+3 -3)
📝 tools/gpustack/provider/gpustack.py (+2 -2)
➕ tools/gpustack/tools/__init__.py (+0 -0)
📝 tools/gpustack/tools/utils.py (+1 -4)

📄 Description

Related Issues or Context

When user configure GPUStack image tool, it will very easily add path /v1 or /v1-openai to the server url, which will cause 404 not found, as the image tool in 0.2 will append v1. We want fix it by removing additional /v1 or /v1-openai.
Snipaste_2025-07-24_23-08-13
Snipaste_2025-07-24_23-38-44
Snipaste_2025-07-24_23-39-08

As the screenshots shows, the tool plugins could config /v1 or /v1-openai path.

This PR contains Changes to LLM Models Plugin

  • My Changes Affect Message Flow Handling (System Messages and User→Assistant Turn-Taking)
  • My Changes Affect Tool Interaction Flow (Multi-Round Usage and Output Handling, for both Agent App and Agent Node)
  • My Changes Affect Multimodal Input Handling (Images, PDFs, Audio, Video, etc.)
  • My Changes Affect Multimodal Output Generation (Images, Audio, Video, etc.)
  • My Changes Affect Structured Output Format (JSON, XML, etc.)
  • My Changes Affect Token Consumption Metrics
  • My Changes Affect Other LLM Functionalities (Reasoning Process, Grounding, Prompt Caching, etc.)
  • Other Changes (Add New Models, Fix Model Parameters etc.)

Version Control (Any Changes to the Plugin Will Require Bumping the Version)

  • I have Bumped Up the Version in Manifest.yaml (Top-Level Version Field, Not in Meta Section)

Dify Plugin SDK Version

  • I have Ensured dify_plugin>=0.3.0,<0.5.0 is in requirements.txt (SDK docs)

Environment Verification (If Any Code Changes)

Local Deployment Environment

  • Dify Version is: , I have Tested My Changes on Local Deployment Dify with a Clean Environment That Matches the Production Configuration.

SaaS Environment

  • I have Tested My Changes on cloud.dify.ai with a Clean Environment That Matches the Production Configuration

🔄 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-official-plugins/pull/1309 **Author:** [@alexcodelf](https://github.com/alexcodelf) **Created:** 7/19/2025 **Status:** ✅ Merged **Merged:** 7/24/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `fix/gpustack-tools` --- ### 📝 Commits (1) - [`a8e12f3`](https://github.com/langgenius/dify-official-plugins/commit/a8e12f3f76658259eeada84e40d4fbc8fe57678c) fix: gpustack image tool compatible url path ### 📊 Changes **4 files changed** (+6 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `tools/gpustack/manifest.yaml` (+3 -3) 📝 `tools/gpustack/provider/gpustack.py` (+2 -2) ➕ `tools/gpustack/tools/__init__.py` (+0 -0) 📝 `tools/gpustack/tools/utils.py` (+1 -4) </details> ### 📄 Description ## Related Issues or Context <!-- ⚠️ NOTE: This repository is for Dify Official Plugins only. For community contributions, please submit to https://github.com/langgenius/dify-plugins instead. - Link Related Issues if Applicable: #issue_number - Or Provide Context about Why this Change is Needed --> When user configure GPUStack image tool, it will very easily add path `/v1` or `/v1-openai` to the server url, which will cause 404 not found, as the image tool in 0.2 will append v1. We want fix it by removing additional /v1 or /v1-openai. <img width="1920" height="836" alt="Snipaste_2025-07-24_23-08-13" src="https://github.com/user-attachments/assets/ef920bf1-a784-4dae-87d2-e5c23c02d1aa" /> <img width="1912" height="925" alt="Snipaste_2025-07-24_23-38-44" src="https://github.com/user-attachments/assets/cf499b08-a8b8-487d-8042-8c74c70dc072" /> <img width="1910" height="920" alt="Snipaste_2025-07-24_23-39-08" src="https://github.com/user-attachments/assets/49edfa2a-cd2e-4e05-9e72-0824524207f8" /> As the screenshots shows, the tool plugins could config /v1 or /v1-openai path. ## This PR contains Changes to *LLM Models Plugin* <!-- LLM Models Test Example: --> <!-- https://github.com/langgenius/dify-official-plugins/blob/main/.assets/test-examples/llm-plugin-tests/llm_test_example.md --> - [ ] My Changes Affect Message Flow Handling (System Messages and User→Assistant Turn-Taking) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] My Changes Affect Tool Interaction Flow (Multi-Round Usage and Output Handling, for both Agent App and Agent Node) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] My Changes Affect Multimodal Input Handling (Images, PDFs, Audio, Video, etc.) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [x] My Changes Affect Multimodal Output Generation (Images, Audio, Video, etc.) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] My Changes Affect Structured Output Format (JSON, XML, etc.) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] My Changes Affect Token Consumption Metrics <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] My Changes Affect Other LLM Functionalities (Reasoning Process, Grounding, Prompt Caching, etc.) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] Other Changes (Add New Models, Fix Model Parameters etc.) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> ## Version Control (Any Changes to the Plugin Will Require Bumping the Version) - [x] I have Bumped Up the Version in Manifest.yaml (Top-Level `Version` Field, Not in Meta Section) <!-- ⚠️ NOTE: Version Format: MAJOR.MINOR.PATCH - MAJOR (0.x.x): Reserved for Significant architectural changes or incompatible API modifications - MINOR (x.0.x): For New feature additions while maintaining backward compatibility - PATCH (x.x.0): For Backward-compatible bug fixes and minor improvements - Note: Each Version Component (MAJOR, MINOR, PATCH) Can Be 2 Digits, e.g., 10.11.22 --> ## Dify Plugin SDK Version - [ ] I have Ensured `dify_plugin>=0.3.0,<0.5.0` is in requirements.txt ([SDK docs](https://github.com/langgenius/dify-plugin-sdks/blob/main/python/README.md)) ## Environment Verification (If Any Code Changes) <!-- ⚠️ NOTE: At Least One Environment Must Be Tested. --> ### Local Deployment Environment - [ ] Dify Version is: <!-- Specify Your Version (e.g., 1.2.0) -->, I have Tested My Changes on Local Deployment Dify with a Clean Environment That Matches the Production Configuration. <!-- - Python Virtual Env Matching Manifest.yaml & requirements.txt - No Breaking Changes in Dify That May Affect the Testing Result --> ### SaaS Environment - [x] I have Tested My Changes on cloud.dify.ai with a Clean Environment That Matches the Production Configuration <!-- - Python Virtual Env Matching Manifest.yaml & requirements.txt --> --- <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 10:24:06 -05:00
yindo closed this issue 2026-02-16 10:24:06 -05:00
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 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-official-plugins#1827
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?