It appears that newusers tries to fetch user information from the API
Reproduction steps
Steps to reproduce the behavior:
Watch KockaLogger output for several hours
See a lot of HTTPErrors leading with a message from the newusers module
Check the username within the Redis key logged in the error message
It doesn't exist
Expected behavior
KockaLogger doesn't log five kilometers (3.10686 feet) of logs and doesn't try five times to retrieve user information just to report a user no longer exists. Maybe the user renamed in the span of 30 minutes since they created their account?
Notes
KockaLogger could also record user ID instead of username to prevent this from happening, but as the feature is supposed to catch spambots, and spambots are unlikely to rename their account shortly after creation, this probably isn't needed.
KockaAdmiralac
commented
1 year ago
Description
It appears that
newuserstries to fetch user information from the APIReproduction steps
Steps to reproduce the behavior:
HTTPErrors leading with a message from thenewusersmoduleExpected behavior
KockaLogger doesn't log five kilometers (3.10686 feet) of logs and doesn't try five times to retrieve user information just to report a user no longer exists. Maybe the user renamed in the span of 30 minutes since they created their account?
Notes
KockaLogger could also record user ID instead of username to prevent this from happening, but as the feature is supposed to catch spambots, and spambots are unlikely to rename their account shortly after creation, this probably isn't needed.