You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of mental notes for later instead of concrete problem description. Please ignore. especially if I closed this. Which means I solved the issue.
SOOOO, some of the maps that the users added is not present in osu api. When we make a cached query, they are always missed. but then they aren't added in cache because requests with them returns empty, which means that they are never cached. which means we make a useless api call every time.
Solution: write a query to remove them from the database once they are found OR cache data wrapped in option to count them into cache. (thinking out loud)
I think I'm going to go with both ways, I will just wrap them into option to keep cache work and skip useless request, log the missing users in db and delete missing beatmaps from database
Detecting this issue isn't hard. If cache miss count and miss requests doesn't match, then we can understand that the maps or users are deleted.
I don't even know if this issue would show up in users (probably will). But they would be harder to deal with. (Let's just log them for now to see if is this even an issue.)
I'm offloading this to my future self as I need to finish higher priority stuff.
The text was updated successfully, but these errors were encountered:
Now that the project is up and running, The banned users shouldn't be a problem as long as they are in the database. We need to have a way to skip them from daily updates.
As for beatmaps, We can have a separate function that spawns a task that runs a database query to find and delete missing beatmaps in our database.
This is more of mental notes for later instead of concrete problem description. Please ignore. especially if I closed this. Which means I solved the issue.
SOOOO, some of the maps that the users added is not present in osu api. When we make a cached query, they are always missed. but then they aren't added in cache because requests with them returns empty, which means that they are never cached. which means we make a useless api call every time.
Solution: write a query to remove them from the database once they are found OR cache data wrapped in option to count them into cache. (thinking out loud)
I think I'm going to go with both ways, I will just wrap them into option to keep cache work and skip useless request, log the missing users in db and delete missing beatmaps from database
Detecting this issue isn't hard. If cache miss count and miss requests doesn't match, then we can understand that the maps or users are deleted.
I don't even know if this issue would show up in users (probably will). But they would be harder to deal with. (Let's just log them for now to see if is this even an issue.)
I'm offloading this to my future self as I need to finish higher priority stuff.
The text was updated successfully, but these errors were encountered: