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

[BUG] level_permissions role ID changed itself on it's own #2856

Closed
Vedinsoh opened this issue Sep 29, 2020 · 0 comments
Closed

[BUG] level_permissions role ID changed itself on it's own #2856

Vedinsoh opened this issue Sep 29, 2020 · 0 comments
Labels
approved bug This is a confirmed bug staged Staged for next version

Comments

@Vedinsoh
Copy link
Contributor

Describe the bug
level_permissions role ID changed itself on it's own, it went from 652209234183979010 to 652209234183979000 (notice the second to last digit).

Bot Info
Bot version (check with @modmail about): 3.5.0
Host method (Heroku, self-host, etc): self-host

To Reproduce
Frankly, I have no idea how this happened. Bot was working just fine for about 2 years (with regular updates) and this happened all of sudden.

Error Logs
Bot was not displaying any specific errors how or when this happened, my staff members only noticed none of the commands suddenly worked for them, in the logs all I saw was:

09/29/20 12:32:10 __main__[1177] - WARNING: User Dark Messiah does not have permission to use this command: `areply` (SUPPORTER).
09/29/20 12:32:10 __main__[1179] - WARNING: CheckFailure: The check functions for command areply failed.

Additional context
One thing I've noticed in the database is that the arrays of role IDs for level_permissions object are not strings like other IDs throughout the config (such as main_category_id or log_channel_id), instead they are Int64 for some reason.

@Vedinsoh Vedinsoh added the maybe: bug An unconfirmed bug label Sep 29, 2020
@fourjr fourjr added approved bug This is a confirmed bug staged Staged for next version and removed maybe: bug An unconfirmed bug labels Nov 10, 2020
@fourjr fourjr closed this as completed in 69d60ab Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved bug This is a confirmed bug staged Staged for next version
Projects
None yet
Development

No branches or pull requests

2 participants