Skip to content

Issue with image operations ("Stream yields empty buffer") #15844

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fluxor99232 opened this issue May 29, 2025 · 2 comments
Open

Issue with image operations ("Stream yields empty buffer") #15844

fluxor99232 opened this issue May 29, 2025 · 2 comments
Labels
in linear Issue or PR has been created in Linear for internal review Needs Feedback Waiting for further input or clarification.

Comments

@fluxor99232
Copy link

Bug Description

Is there some fundamental issue with the handling of images in the most recent version?

All image operations of the Edit Image node on any type of image (e.g. .PNG, .jpg) and any source (e.g. read from disk, from telegram message) fail with this error:

Problem in node ‘Edit Image‘
Stream yields empty buffer

Also, maybe related, maybe not, I noticed the "Image Size" option on the Telegram Trigger node does not seem to have any effect. Tried on a .PNG file with all settings from "Small" to "Extra Large" without any effect on the saved image.

I'm using the official Docker image and version 1.93.0.

To Reproduce

{
  "nodes": [
    {
      "parameters": {
        "fileSelector": "/queues/music-recognize/**/*",
        "options": {}
      },
      "type": "n8n-nodes-base.readWriteFile",
      "typeVersion": 1,
      "position": [
        -440,
        -600
      ],
      "id": "223c1364-da24-4419-900c-6e473c4d5d97",
      "name": "Read/Write Files from Disk"
    },
    {
      "parameters": {},
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        -660,
        -700
      ],
      "id": "eba6bb6c-205f-4670-9da3-fe5f6510975c",
      "name": "When clicking ‘Test workflow’"
    },
    {
      "parameters": {
        "operation": "blur",
        "options": {}
      },
      "type": "n8n-nodes-base.editImage",
      "typeVersion": 1,
      "position": [
        -120,
        -840
      ],
      "id": "68714d80-b847-47a1-ab22-5b5406c3946e",
      "name": "Edit Image"
    }
  ],
  "connections": {
    "Read/Write Files from Disk": {
      "main": [
        [
          {
            "node": "Edit Image",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "When clicking ‘Test workflow’": {
      "main": [
        [
          {
            "node": "Read/Write Files from Disk",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Edit Image": {
      "main": [
        []
      ]
    }
  },
  "pinData": {},
  "meta": {
    "templateCredsSetupCompleted": true,
    "instanceId": "bd50e80c742106c8130a8bba5a47bcc54e183f1865ed03f3a23ac8ad32e5ef45"
  }
}

Expected behavior

Edit Image node operations should complete successfully.

Operating System

Kubernetes

n8n Version

1.93.0

Node.js Version

20.19.0

Database

SQLite (default)

Execution mode

main (default)

@Joffcom
Copy link
Member

Joffcom commented May 29, 2025

Hey @fluxor99232,

We have created an internal ticket to look into this which we will be tracking as "GHC-2248"

@Joffcom Joffcom added the in linear Issue or PR has been created in Linear for internal review label May 29, 2025
@Joffcom
Copy link
Member

Joffcom commented May 30, 2025

Hey @fluxor99232,

Thanks for reporting this issue! We’ve attempted to reproduce the problem, but unfortunately, we weren’t able to replicate it. It’s possible there was some environmental or other variable that prevented us from seeing the same behavior.

Image

If you’re still encountering this issue, please provide any additional details or steps to reproduce it, and we’d be happy to investigate further. Thanks for your understanding!

Are you sure you are using the official docker image and not a custom image or running n8n from npm? Normally we see this error when people run n8n locally as they don't have everything installed that the docker image uses. Another thing to check could be that the binary data is actually in the input to be edited as well.

@Joffcom Joffcom added the Needs Feedback Waiting for further input or clarification. label May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in linear Issue or PR has been created in Linear for internal review Needs Feedback Waiting for further input or clarification.
Projects
None yet
Development

No branches or pull requests

2 participants