#Discordeno v19

1 messages ยท Page 1 of 1 (latest)

tall skiff
#

Starting Error

elder dune
tall skiff
#

there is a bug in discordeno where it is not automatically setting the number of shards

#

unlike before

#

where it used to do that earlier

elder dune
#

oo okay ๐Ÿ˜›

leaden sandal
#

@lusty venture did we break lastShardId somehow?

lusty venture
#

@tall skiff v19?

#

Could you give a MRE?

leaden sandal
#

If he can try the commit before vs that commit

#

To see if that change caused it

lusty venture
#

That should tell as well yea

#

dfbee47 - before
a3e6551 - that commit

leaden sandal
#

@tall skiff

tall skiff
#
const sessionInfo = await bot.rest.getSessionInfo();
console.log(sessionInfo);
bot.gateway.totalShards = sessionInfo.shards;
bot.gateway.lastShardId = sessionInfo.shards - 1;
bot.start();

This is my fix

leaden sandal
#

@tall skiff can u check what broke exactly

tall skiff
# leaden sandal <@794921502230577182> can u check what broke exactly

From bot.ts in bot package

      // @ts-expect-error should this work
      if (typeof Deno !== 'undefined') {
        // @ts-expect-error should this work
        const katsura = await import('https://x.nest.land/[email protected]/src/discordenoFixes/gatewaySocket.ts')

        await katsura(bot.gateway)
      }

      if (!options.gateway?.connection) {
        bot.gateway.connection = await bot.rest.getSessionInfo();
        //Why is totalShards and lastShardId not updated here?
      }
      return await bot.gateway.spawnShards()
    },
leaden sandal
#

interesting

#

why was it working before this ๐Ÿค”

#

@tall skiff dfbee47

#

do u have the error with that commit?

lusty venture
leaden sandal
#

Yep odd

mortal brook
lusty venture
mortal brook
lusty venture
#

Has it ever worked

mortal brook
#

doubt it

lusty venture
#

Cuz it shouldn't

lusty venture
#

To see if it used to work and broken now

mortal brook
lusty venture
#

What's that link aboutm

#

gtg I'll see later

mortal brook
lusty venture
#

That's another commit + idk if it's the same as this connection thing

mortal brook
#

hold on

#

does this cause a problem in node? kappa_lul

lusty venture
#

The message you linked looks like another issue, the one in this is another