Opened 10 years ago
Closed 9 years ago
#694 closed defect (bug) (worksforme)
slackbot should only post mentions once a day
Reported by: | SergeyBiryukov | Owned by: | nacin |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Communication (Matrix, Slack, IRC) | Keywords: | |
Cc: |
Description
ircbot only posted comments to Trac tickets once a day.
Looks like slackbot does not have the same restriction, which results in duplicate comments (see the screenshot).
Attachments (1)
Change History (9)
#3
follow-up:
↓ 5
@
10 years ago
There seems to be a slight bug here that makes the slack mentions get pushed in twice as well (so it's mentioned once, but it gets two "mention" entries in trac)
This ticket was mentioned in Slack in #meta by clorith. View the logs.
10 years ago
#5
in reply to:
↑ 3
@
10 years ago
Replying to Clorith:
There seems to be a slight bug here that makes the slack mentions get pushed in twice as well (so it's mentioned once, but it gets two "mention" entries in trac)
I think the second mention comes from Slack itself displaying the ticket summary.
#6
follow-up:
↓ 7
@
10 years ago
- Component changed from Trac to Slack
- Owner set to nacin
- Status changed from new to accepted
I've never seen a second mention, and the bot is smart enough to avoid cross-posting the ticket summary. It *could* have happened due to a misconfiguration on our part (such as two outgoing webhooks watching the same Slack channel). If you ever see it again, then please open a new ticket as a bug.
I have throttling code for this done, but I wasn't able to debug why it wasn't working properly. I'll look into it.
#7
in reply to:
↑ 6
@
10 years ago
Replying to nacin:
I've never seen a second mention, and the bot is smart enough to avoid cross-posting the ticket summary. It *could* have happened due to a misconfiguration on our part (such as two outgoing webhooks watching the same Slack channel). If you ever see it again, then please open a new ticket as a bug.
Just noticed a duplicate summary in #forums, see #831.
A smarter restriction could be better, when a ticket is mentioned it could start a timer for like 15 minutes and reset every time it is mentioned again. Then it will report all disconnected occurrences.
Just an idea.