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

Missing Reminders #1916

Closed
HassanAbouelela opened this issue Oct 27, 2021 · 3 comments
Closed

Missing Reminders #1916

HassanAbouelela opened this issue Oct 27, 2021 · 3 comments
Labels
a: backend Related to internal functionality and utilities (error_handler, logging, security, utils and core) a: utility Related to utility commands: (bot, eval, extensions, jams, reminders, snekbox, utils) p: 1 - high High Priority status: approved The issue has received a core developer's approval t: bug Something isn't working

Comments

@HassanAbouelela
Copy link
Member

For a while now, I've been noticing that my longer reminders are usually removed from the database, without being sent, leading to many missing reminders. I've been digging into it for a while now, but there is nothing noteworthy as far as I could tell.

There is nothing in logs, and there is nothing in the bot behavior that should block reminders. The most recent example I have was scheduled for 1 minute after another reminder. The other reminder was delivered, mine wasn't. I won't be linking the examples here because they are all in internal channels.

To help continue debugging this, and because it is so difficult to reproduce, I'm going to modify the reminder task to not delete entries from the DB, and instead mark them as inactive. I'll continue tracking this issue here.

@HassanAbouelela HassanAbouelela added t: bug Something isn't working a: backend Related to internal functionality and utilities (error_handler, logging, security, utils and core) p: 2 - normal Normal Priority a: utility Related to utility commands: (bot, eval, extensions, jams, reminders, snekbox, utils) status: approved The issue has received a core developer's approval labels Oct 27, 2021
@HassanAbouelela
Copy link
Member Author

@Senjan21 managed to find in the logs that there are in fact errors being logged (and we accidentally took down the entire community's infra 😅). user appears to be none in ensure_valid_reminder (my guess is because it's called during bot startup, which most likely means the cache is unpopulated. Can no longer confirm, as the logs have been deleted).

I have a new solution in mind, and will be PRing that instead.

@HassanAbouelela
Copy link
Member Author

I've spoken with Zig, and we think it's best if on top of the other PR, we try to decouple the reliance on member objects for this cog where possible. Replacing member.mention with manual mentions, and adding a fallback default for role checks are examples of how we could go about that.

HassanAbouelela added a commit that referenced this issue Feb 4, 2022
The reminders cog is being temporarily disabled until issue #1916 is
resolved.

Signed-off-by: Hassan Abouelela <[email protected]>
@wookie184
Copy link
Contributor

I think the original issue here was fixed, though I noticed another way reminders may go missing, which i've opened a new issue for #3015.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a: backend Related to internal functionality and utilities (error_handler, logging, security, utils and core) a: utility Related to utility commands: (bot, eval, extensions, jams, reminders, snekbox, utils) p: 1 - high High Priority status: approved The issue has received a core developer's approval t: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants