Duplicate Meta digest emails this morning

AI-generated summary

Duplicate Meta digest emails issue

jesselperry reported receiving duplicate Meta digest emails with different content, indicating the issue was on Discourse’s end. tobiaseigen suggested it might be due to test accounts, but jesselperry clarified it was the same email address. cpradio mentioned someone else experienced the issue as well.

zogstrip confirmed the issue and found two bugs associated with it. The bugs were fixed in a commit. zogstrip stated the issue was introduced two days prior and that beta 8 users are not affected.

However, Korben00 reported experiencing the issue with beta 9. codinghorror assured that the issue is already fixed and users just need to update to the latest commit.

I got duplicate Meta digest emails this morning. One at 2:47am and 8:47am. I know these aren’t duplicates because of my email provider (FastMail & MailRoute), because they both have slightly different content. So they were both generated from Discourse.

1 Mi Piace

do you have test accounts? e.g. using foo@gmail.com and foo+test@gmail.com?

No. Same email address on both. I’ve been getting digest emails for a while. First time I’ve received duplicates.

anything exciting in the error logs?

Ah. just realized you’re talking about meta. I can’t help with this. :wink:

I know someone else who got multiple digests this morning too. I myself do not get any emails (I have them disabled).

Confirmed. I can see both in the logs. Something’s wrong here :frowning: Will have a look.

3 Mi Piace

Thanks @jesselperry for reporting this issue. Turns out there were 2 bugs associated to that issue…

https://github.com/discourse/discourse/commit/d51019ee53e524cb18829cc16e918c81b84136e9

6 Mi Piace

:dizzy: Great quick work.

Do you know if this was recently introduced? Or if I’m on beta 8 am I fine not upgrading?

It was introduced 2 days ago.

beta 8 is :ok_hand:

3 Mi Piace

Hi

same bug on duplicate email digests here with the beta9.
I hope it will be fixed soon.

Thank you

It’s already fixed – nothing to do, just update to the very latest commit.

2 Mi Piace