Production instance's caching behaving very differently
So this one is a very odd one for me. I have different parts of my code where caching works fine on my test bot (5 servers) vs my production bot (16k servers).
One example is this command where I'm using
guild.getMemberOrNull to display a list of users (IDs coming from my DB) into strings with their usernames. The problem is that it takes a long time to resolve the response. I would understand if it took long to resolve once, and then subsequent calls didn't, because they are supposed to be cached (EntitySupplyStrategy.cacheWithCachingRestFallback), but every time, it takes a long time. We have tried to switching strategies for this particular command, like using cache only, and it would result in a lot of users just not being found.
Now, recently, I added some channel permission checks to some task I have. And I noticed that since then, the task is taking a long time to complete. Upon checking my logs, I see a bunch of requests to https://discord.com/api/v10/guilds/<guildId>/members/<myBotId>, sometimes even making two calls within the same second (there is another permission check further down the task's execution)...Solution:
Sentry DSN not detected
So I was redoing how I start the Sentry extension, to use
enableIfDSN instead of doing the null check myself, and I noticed the Sentry extension was failing to initialize, and reverted it and it is still failing. So I don't know if this could have been caused by the latest changes? My bot is unable to start now if a Sentry DSN is set.
I put a breakpoint in SentryAdapter.init and I can see that the DSN is available:
Then on Sentry.java, line 187, there is a applyOptionsConfiguration function, it takes optionsConfiguration (which still has the settings there) and options, which is empty....Solution:
I've pushed, should be up in 10-15 mins, hopefully it works
translations not translating
https://github.com/mazziechai/kose-kata/blob/main/src/main/kotlin/cafe/ferret/kosekata/extensions/UtilityExtension.kt
see image for result when calling /clear
why does this happen? i thought
translate pulls from the bundle in the extension? it works elsewhere...