#TypeError: thread.members._add is not a

1 messages · Page 1 of 1 (latest)

ruby bough
#

This is super strange because this shouldn't happen ablobsweats do you get this consistently?

ocean salmon
#

what version you on

spiral vapor
#

I'm getting it only on launch

ocean salmon
spiral vapor
#

Please let me explain before sending questions

ocean salmon
spiral vapor
#

No help needed

ruby bough
ocean salmon
#

bye

ruby bough
#

Let me deal with this, kthx

spiral vapor
#

bye

ruby bough
spiral vapor
#

Great

#

So

ocean salmon
#

its due to the version thinkingLol

ruby bough
#

as I was saying

lofty siren
#

What a champ

carmine magnet
#

lmfao that made me laugh, sorry I'll be lurking Shrug

ruby bough
#

Do you change caches at all?

spiral vapor
#

We have quite a lot of shards (30) and while launching we got this error, not always but strangely we got the error this time togetherwith the reduce error. I reverted the djs version and the issue was gone

#

I will send you the full launch log

ruby bough
#

the reduce errors are unrelated to the thread stacktrace, different issues

spiral vapor
#

As you see all our clusters weren't booting and crashing, some with the reduce error, others with the thread.members

ruby bough
#

how tf would we have a thread cached but members non existent, HUH

spiral vapor
#

Its a public bot, so really difficult to trace when and where this issue happened

ruby bough
#

Can you maybe inject some code to log the thread ?

spiral vapor
#

I can't, I have no idea on which server or guild this happened

ruby bough
# 
typeof thread.members._add !== 'function' && console.log(`Unexpected broken thread in guild ${thread.guild.id} (${thread.id}, ${thread.name})`, thread, thread.members);
#

can you add that before that reduce line?

spiral vapor
#

In the discord.js code?

ruby bough
#

yap, innn

#

/home/container/node_modules/discord.js/src/client/actions/ThreadMembersUpdate.js

#

you can use patch-package/yarn patch/pnpm patch

spiral vapor
#

I will do that for you, but it is possible that we have no result for a couple of hours or maybe days

ruby bough
#

thats fine, but in the event you do get this again, feel free to poke me

#

@spiral vapor do you have any custom client options btw? Specifically any that touch caches?

spiral vapor
# ruby bough <@355044873994371073> do you have any custom client options btw? Specifically an...

makeCache: Options.cacheWithLimits({
...Options.DefaultMakeCacheSettings,
AutoModerationRuleManager: 0,
ApplicationCommandManager: 0,
DMMessageManager: 0,
GuildBanManager: 0,
GuildForumThreadManager: 0,
GuildInviteManager: 0,
GuildMemberManager: {
keepOverLimit: member => member.id === member.client.user.id,
maxSize: 50
},
GuildScheduledEventManager: 0,
GuildStickerManager: 0,
PresenceManager: 0,
ReactionManager: 0,
ReactionUserManager: 0,
StageInstanceManager: 0,
VoiceStateManager: 0,
MessageManager: 0
})

#

partials: [Partials.Message, Partials.Channel, Partials.User, Partials.GuildMember],
failIfNotExists: false,

#

These client options we got related to cache i think

#

And some sweepers

#

@ruby bough

ruby bough
#

ok so not what i was thinking off

#

strangeee

#

best bet is to add that console log and see if it comes up

spiral vapor
#

Okay

#

Will keep you updated

zinc bloom
#

I got this as well today on boot up, using 14.15.3