Open chrissank opened 3 years ago
this happens when there are less than 10 (or something) events that have undefined descriptions over the next week, so it starts to grab the next event in the repeated event as well
Bug still exists, reproduced in dev:
/initialize
in any of the channels in slack
Sometimes after a /initialize Minerva sends two initialize messages for the same event (denoted by having the same names). Only the first (i.e. the event that occurs the earliest) should be used.