Image Streaming Incompatibility with "Fluidly stream large external response chunks" Setting #2792

New Issue

GiteaMirror · 2025-11-11T15:14:34-06:00

GiteaMirror commented

2025-11-11 15:14:34 -06:00

Originally created by @jaim12005 on GitHub (Nov 23, 2024).

Description
When the "Fluidly stream large external response chunks" setting is enabled in Settings -> Interface, image generation responses are incorrectly split into chunks, causing the raw base64/HTML data to be displayed as text instead of rendering as images.

Current Behavior

With streaming enabled: Images appear as walls of text (raw base64/HTML data)
With streaming disabled: Images render correctly

Technical Details
The issue occurs because the streaming feature splits large response chunks, which breaks the HTML image tag structure required for proper rendering. This affects any manifold function that returns images, not just Flux.

Suggested Solutions

Add a special case in the streaming logic to detect and preserve image tags/responses
Add a new message type for images that bypasses the streaming chunking
Modify the streaming chunk size to ensure image responses stay intact

Workaround
Currently, users must disable "Fluidly stream large external response chunks" in Settings -> Interface for images to display correctly. This has been documented in the manifold function, but it would be better to have a proper fix that allows both streaming and image rendering to work together.

Impact
This affects all users trying to use image generation while having the streaming feature enabled, which is likely a common configuration given it's a UI setting.

Let me know if you need any additional information or would like me to test potential solutions.

Originally created by @jaim12005 on GitHub (Nov 23, 2024). **Description** When the "Fluidly stream large external response chunks" setting is enabled in Settings -> Interface, image generation responses are incorrectly split into chunks, causing the raw base64/HTML data to be displayed as text instead of rendering as images. **Current Behavior** - With streaming enabled: Images appear as walls of text (raw base64/HTML data) - With streaming disabled: Images render correctly **Technical Details** The issue occurs because the streaming feature splits large response chunks, which breaks the HTML image tag structure required for proper rendering. This affects any manifold function that returns images, not just Flux. **Suggested Solutions** 1. Add a special case in the streaming logic to detect and preserve image tags/responses 2. Add a new message type for images that bypasses the streaming chunking 3. Modify the streaming chunk size to ensure image responses stay intact **Workaround** Currently, users must disable "Fluidly stream large external response chunks" in Settings -> Interface for images to display correctly. This has been documented in the manifold function, but it would be better to have a proper fix that allows both streaming and image rendering to work together. **Impact** This affects all users trying to use image generation while having the streaming feature enabled, which is likely a common configuration given it's a UI setting. Let me know if you need any additional information or would like me to test potential solutions.

GiteaMirror closed this issue