Skip to content
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

IMAP Trigger Node Binary File Attachments Corrupted #9313

Open
darrengoldner opened this issue May 6, 2024 · 6 comments
Open

IMAP Trigger Node Binary File Attachments Corrupted #9313

darrengoldner opened this issue May 6, 2024 · 6 comments
Labels
in linear Issue or PR has been created in Linear for internal review

Comments

@darrengoldner
Copy link

Bug Description

Beginning around approximately commit 9f87cc2, all binary files retrieved from the IMAP trigger nodes in my workflow are overstated by approximately 2X.

To Reproduce

Create a new IMAP trigger node with credentials to any IMAP mailbox with file attachments.
Test trigger with filter criteria that include a message with attachments.
Compare binary data for attachment(s) vs expectactions

Expected behavior

Binary file attachments should be retrieved exactly as they are represented in the IMAP mailbox.

Operating System

Ubuntu 22.04.3 LTS

n8n Version

1.38.2

Node.js Version

18.18.0

Database

PostgreSQL

Execution mode

main (default)

@Joffcom
Copy link
Member

Joffcom commented May 8, 2024

Hey @darrengoldner,

Are the files actually bigger and corrupted or do we just show a larger size in the UI?

@darrengoldner
Copy link
Author

Bigger and corrupted

@Joffcom
Copy link
Member

Joffcom commented May 10, 2024

@darrengoldner I have managed to reproduce and have created NODE-1344 as the internal ticket to fix this.

@Joffcom Joffcom added the in linear Issue or PR has been created in Linear for internal review label May 10, 2024
@darrengoldner
Copy link
Author

would it be possible to merge this fix into the Latest release? It was in 1.41.1 and then we moved up to 1.42.1 on latest track. Or is there a timeline for one of the latter minor versions which have the patch to become the latest?

@netroy
Copy link
Member

netroy commented May 30, 2024

this fix should already be in the latest release. are you still seeing this issue ?

@darrengoldner
Copy link
Author

Yes. AFAICT the behavior returned in 1.42.1. It had been resolved in 1.41.1

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
Projects
None yet
Development

No branches or pull requests

3 participants