[PR #754] [MERGED] feat: Guess mime type by filename for non-image outputs in ComfyUI pl… #1534

Closed
opened 2026-02-16 10:23:14 -05:00 by yindo · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-official-plugins/pull/754
Author: @oubeichen
Created: 4/18/2025
Status: Merged
Merged: 4/21/2025
Merged by: @crazywoola

Base: mainHead: comfyui-guess-mimetype


📝 Commits (2)

  • d0165bf feat: Guess mime type by filename for non-image outputs in ComfyUI plugin.
  • 027a751 chore: Update dify_plugin version constraint in requirements.txt in ComfyUI plugin

📊 Changes

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

View changed files

📝 tools/comfyui/manifest.yaml (+1 -1)
📝 tools/comfyui/requirements.txt (+1 -1)
📝 tools/comfyui/tools/comfyui_client.py (+7 -2)
📝 tools/comfyui/tools/comfyui_workflow.py (+3 -2)

📄 Description

…ugin.

ComfyUI does not only support image generation, but can also generate audio, video, and model files.

All output files are stored under the "images" field in ComfyUI history JSON regardless of their type, refer to https://github.com/comfyanonymous/ComfyUI/blob/7ecd5e961465d9bb20fb12b7068e1930da875b0e/comfy_extras/nodes_video.py

Use mimetypes.guess_type() to determine the correct mime type based on the filename, fallback to image/png if unable to guess.

This helps workflows handle different output file types correctly.

Related Issues or Context

This PR contains Changes to Non-Plugin

  • Documentation
  • Other

This PR contains Changes to Non-LLM Models Plugin

  • I have Run Comprehensive Tests Relevant to My Changes

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, 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'm Using dify_plugin>=0.1.0,<0.2.0 in requirements.txt (SDK docs)

Environment Verification (If Any Code Changes)

Local Deployment Environment

  • Dify Version is: 1.1.0 , 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/754 **Author:** [@oubeichen](https://github.com/oubeichen) **Created:** 4/18/2025 **Status:** ✅ Merged **Merged:** 4/21/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `comfyui-guess-mimetype` --- ### 📝 Commits (2) - [`d0165bf`](https://github.com/langgenius/dify-official-plugins/commit/d0165bfa4460adf8a56dd07f2f8a0bcac508d6cf) feat: Guess mime type by filename for non-image outputs in ComfyUI plugin. - [`027a751`](https://github.com/langgenius/dify-official-plugins/commit/027a751b9515cfe288af0b6d800baf194b796f89) chore: Update dify_plugin version constraint in requirements.txt in ComfyUI plugin ### 📊 Changes **4 files changed** (+12 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `tools/comfyui/manifest.yaml` (+1 -1) 📝 `tools/comfyui/requirements.txt` (+1 -1) 📝 `tools/comfyui/tools/comfyui_client.py` (+7 -2) 📝 `tools/comfyui/tools/comfyui_workflow.py` (+3 -2) </details> ### 📄 Description …ugin. ComfyUI does not only support image generation, but can also generate audio, video, and model files. All output files are stored under the "images" field in ComfyUI history JSON regardless of their type, refer to https://github.com/comfyanonymous/ComfyUI/blob/7ecd5e961465d9bb20fb12b7068e1930da875b0e/comfy_extras/nodes_video.py Use mimetypes.guess_type() to determine the correct mime type based on the filename, fallback to image/png if unable to guess. This helps workflows handle different output file types correctly. ## 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 --> ## This PR contains Changes to *Non-Plugin* <!-- Put an `x` in all the boxes that apply by replacing [ ] with [x] For example: - [x] Documentation --> - [ ] Documentation - [ ] Other ## This PR contains Changes to *Non-LLM Models Plugin* - [ ] I have Run Comprehensive Tests Relevant to My Changes <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> ## 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, 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 - [x] I'm Using `dify_plugin>=0.1.0,<0.2.0` 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 - [x] Dify Version is: 1.1.0 <!-- 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 - [ ] 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:23:14 -05:00
yindo closed this issue 2026-02-16 10:23:14 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#1534