distribute method should not cached ThreadPool

[malacca]

the issue code

https://github.com/grammyjs/runner/blob/main/src/distribute.ts#L46

Reproduction code

bot.js

const { Bot, session } = require('grammy');
const {
  run,
  distribute,
  BotWorker,
  sequentialize,
} = require('@grammyjs/runner');
const {
  isMainThread,
  setEnvironmentData,
  getEnvironmentData,
} = require('node:worker_threads');

function getSessionKey(ctx) {
  return ctx.chat?.id.toString();
}

function initialSessionValue() {
  return {};
}

function ComposeBot(bot, inThread) {
  bot.on('msg', async (ctx) => {
    console.log(inThread, ctx);
  });
  return bot;
}

async function StartBot(token, { workerCount = 4, ...config } = {}) {
  const bot = new Bot(token, config);
  bot.use(sequentialize(getSessionKey));
  bot.use(session({ getSessionKey, initial: initialSessionValue }));

  if (workerCount > 1) {
    setEnvironmentData('BotToken', token);
    bot.use(distribute(__filename));
  } else {
    ComposeBot(bot, false);
  }
  const runner = run(bot);
  const stopRunner = () => runner.isRunning() && runner.stop();
  process.once('SIGINT', stopRunner);
  process.once('SIGTERM', stopRunner);
}

module.exports = {
  StartBot,
};

if (!isMainThread) {
  const token = getEnvironmentData('BotToken');
  ComposeBot(new BotWorker(token), token);
}

runner.js

const { StartBot } = require('./bot');
StartBot('Token__A');
StartBot('Token__B');

Since the child threads always use the same file
the cache will cause the child threads to not be created correctly 😳

[KnorpelSenf]

This isn't at all how this library is supposed to be used.

What's your point? Are you saying that you want to create a new worker thread for each new update?

[malacca]

i want create a wrapper of grammy Bot

that support config workerCount

https://github.com/grammyjs/runner/blob/main/src/distribute.ts#L46

when I start multiple bots by wrapper function,

Because specifier is always the same file, only the first create ThreadPool really,

[KnorpelSenf]

Yeah the distribute middleware wasn't written with the fact in mind that some people could use it to process updates from unrelated bots. I'd be happy to accept a pull request that adds this feature!