Baileys
Baileys copied to clipboard
WhiskeySockets
Flush Buffer
Thanks for your contribution.
The next step is to wait for review and approval to merge it to main repository
The community can help reacting with a thumb up (:thumbsup:) for approval and rocket (:rocket:) for who has tested it.
To test this PR you can run the following command below:
# NPM
npm install @whiskeysockets/baileys@makanSukros/Baileys#master
# YARN v2
yarn add @whiskeysockets/baileys@makanSukros/Baileys#master
@makanSukros , could you explain this change?
to solve the problem of messages.upsert not getting through sometimes
@makanSukros no, this is not fix the root cause
I am who made this quick fix in my repo https://github.com/kbiits/Whiskey-Baileys
please don't just copy paste and made a PR for fixing, you need to analyze the root cause
my quick fix is not solve the root cause
I personally don't experience this issue. Maybe there is something wrong with your code/ misconfigure or missing auth/ something else. I suggest to close this pr and investigate the root cause as @kbiits suggest.
I personally don't experience this issue. Maybe there is something wrong with your code/ misconfigure or missing auth/ something else. I suggest to close this pr and investigate the root cause as @kbiits suggest.
No, I don't thinks it's from the code / configuration. A lot of people experience this issue. I still can't figure out what the root cause is and why the buffer is not flushed. Currently I don't have any spare time to investigate it more. But what I can say is it's not from the client code / configuration
I don't know if this could be related to the timedouts that occur with me and others using the code. But after some time connected it becomes unfeasible to use the message sending and number validation methods, if your defaultQueryTimeoutMs is not set to undefined a TimedOut error message will be printed in the terminal, at least the only simple way to solve this is by stopping the application and starting again, programmatically to do this becomes somewhat complex, as in my case I had to use child_process. Anyway, I already opened an issue on the old repo to talk about the subject and almost no one responded, but talking to some developers who use Baileys, everyone goes through this problem, including investigating a little deeper into the issues related to this subject this problem is even a little old and at least no one has been able to solve this problem at the root, not even Adi himself
Não sei se isso pode estar relacionado aos tempos limite que ocorrem comigo e com outras pessoas usando o código. Mas depois de algum tempo conectado torna-se inviável usar os métodos de envio de mensagens e validação de número, se o seu defaultQueryTimeoutMs não estiver definido como undefined uma mensagem de erro TimedOut será impressa no terminal, pelo menos a única maneira simples de resolver isso é parando o aplicativo e começando novamente, programaticamente para fazer isso se torna um pouco complexo, como no meu caso eu tive que usar child_process. Enfim, já abri uma edição no antigo repo para falar sobre o assunto e quase ninguém respondeu, mas conversando com alguns desenvolvedores que usam Baileys, todo mundo passa por esse problema, inclusive investigando um pouco mais a fundo nas questões relacionadas a esse assunto esse problema é até um pouco antigo e pelo menos ninguém conseguiu resolver esse problema na raiz, nem mesmo o próprio Adi
tell me how you solved it, this problem is a headache.
