This repository was archived by the owner on Feb 7, 2026. It is now read-only.
Fix a bug which returns KeyError when modifying user level#311
Merged
Fix a bug which returns KeyError when modifying user level#311
KeyError when modifying user level#311Conversation
When the levelling db library attempts to add or remove levels from a user (through framework), it ends up failing and returning a `KeyError` exception. This was because in the levelling db library, the `add_levels()` and `remove_levels()` methods were attempting to modify the `levels` value (non-existant) instead of the `level` value (actual key name). This patch aims at resolving this issue.
notsniped
added
priority:critical
area:storage
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When the levelling db library attempts to add or remove levels from a user (through framework), it ends up failing and returning a
KeyErrorexception.Reason
This was because in the levelling db library, the
add_levels()andremove_levels()methods were attempting to modify thelevelsvalue (non-existant) instead of thelevelvalue (actual key name).Conclusion
This patch aims at resolving this issue and providing a bug-free user experience.