You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only difference i can see between this issue and the others that got through is that it has two labels, rather than one. No idea whether that is significant.
So, the problem is that the digest notifier looks at the labels on the issue at the time of its creation, not labels that might have been added after the issue is created.
I'll need to think some more as to what the right behavior should be given the intended usage here and elsewhere (input welcome though!)
I've noticed a couple of times recently that new issues have not found their way into email notifications.
Here's an example from today's notifications. w3c/i18n-issues#2
It should have been listed at https://lists.w3.org/Archives/Public/public-i18n-cjk/2018AprJun/0007.html with the others.
The rule is:
The only difference i can see between this issue and the others that got through is that it has two labels, rather than one. No idea whether that is significant.
However, this was notified via another rule to https://lists.w3.org/Archives/Public/www-international/2018AprJun/0033.html. Interestingly, no labels are shown next to the link in that notification.
Seems odd, since the labels were set at around the same time as the issue was created.
This is, obviously, a significant problem when it comes to tracking new comments. Any idea where the problem originates?
The text was updated successfully, but these errors were encountered: