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

fix(Gmail Trigger Node): Change Gmail Trigger dedupe logic #10717

Conversation

ShireenMissi
Copy link
Contributor

Summary

This PR changes how GMail Trigger node handles duplicate email by changing the comparison against latest email date

Related Linear tickets, Github issues, and Community forum posts

https://linear.app/n8n/issue/NODE-1601/community-issue-gmail-trigger-fetching-duplicate-emails-again
#10470

Review / Merge checklist

  • PR title and summary are descriptive. (conventions)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

@ShireenMissi ShireenMissi changed the title fix(GMail Trigger): Change Gmail Trigger dedupe logic fix(GMail Trigger Node): Change Gmail Trigger dedupe logic Sep 6, 2024
@ShireenMissi ShireenMissi changed the title fix(GMail Trigger Node): Change Gmail Trigger dedupe logic fix(Gmail Trigger Node): Change Gmail Trigger dedupe logic Sep 6, 2024
Copy link
Member

@elsmr elsmr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be nice to have a test, but I understand it's not easy at this point. Let's write some tests for this trigger as part of the upcoming tech debt week

@elsmr elsmr added the tests-needed This PR needs additional tests label Sep 9, 2024
Copy link

cypress bot commented Sep 9, 2024

n8n    Run #6788

Run Properties:  status check passed Passed #6788  •  git commit b5966cf734: 🌳 🖥️ browsers:node18.12.0-chrome107 🤖 ShireenMissi 🗃️ e2e/*
Project n8n
Branch Review node-1601-community-issue-gmail-trigger-fetching-duplicate-emails-again
Run status status check passed Passed #6788
Run duration 04m 42s
Commit git commit b5966cf734: 🌳 🖥️ browsers:node18.12.0-chrome107 🤖 ShireenMissi 🗃️ e2e/*
Committer Shireen Missi
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 425
View all changes introduced in this branch ↗︎

Copy link
Contributor

github-actions bot commented Sep 9, 2024

✅ All Cypress E2E specs passed

@n8n-assistant n8n-assistant bot added n8n team Authored by the n8n team node/improvement New feature or request labels Sep 10, 2024
@ShireenMissi ShireenMissi merged commit 9f3e03d into master Sep 10, 2024
32 of 34 checks passed
@ShireenMissi ShireenMissi deleted the node-1601-community-issue-gmail-trigger-fetching-duplicate-emails-again branch September 10, 2024 07:55
@github-actions github-actions bot mentioned this pull request Sep 11, 2024
@Joffcom
Copy link
Member

Joffcom commented Sep 11, 2024

Got released with [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
n8n team Authored by the n8n team node/improvement New feature or request Released tests-needed This PR needs additional tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants