Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client.disconnect() has been executed, but _updateLoop not fully uninstalled #615

Open
kaadon opened this issue Nov 29, 2023 · 5 comments
Open

Comments

@kaadon
Copy link

kaadon commented Nov 29, 2023

[2023-11-29T10:52:12.165] [INFO] - [Running gramJS version 2.19.9]
[2023-11-29T10:52:12.167] [INFO] - [Connecting to 91.108.56.133:80/TCPFull...]
[2023-11-29T10:52:12.293] [INFO] - [Connection to 91.108.56.133:80/TCPFull complete!]
[2023-11-29T10:52:12.294] [INFO] - [Using LAYER 166 for initial connect]
[2023-11-29T10:52:15.640] [WARN] - [Disconnecting...]
[2023-11-29T10:52:15.640] [INFO] - [Disconnecting from 91.108.56.133:80/TCPFull...]
[2023-11-29T10:52:15.642] [INFO] - [connection closed]

Error: TIMEOUT
    at /Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:244:85
    at async attempts (/Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:228:20)
    at async _updateLoop (/Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:180:17)

Error: TIMEOUT
    at /Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:244:85
    at async attempts (/Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:228:20)
    at async _updateLoop (/Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:180:17)

Error: TIMEOUT
    at /Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:244:85
    at async attempts (/Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:228:20)
    at async _updateLoop (/Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:180:17)

Error: TIMEOUT
    at /Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:244:85
    at async attempts (/Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:228:20)
    at async _updateLoop (/Volumes/SourceData/webhook/node/telegram_protocol_number/node_modules/telegram/client/updates.js:180:17)
@davie-robertson
Copy link

I'm also getting this in 2.19.10 - I didn't see this before on previous versions

@andrezero0
Copy link

conseguirão achar uma solução

@davie-robertson
Copy link

I've started using await client.destroy(); instead of disconnect - not sure if this is going to cause me a problem long term, but it gets rid of this issue/bug

@andrezero0
Copy link

na 2.19.10

@SergeyTverye
Copy link

I've started using await client.destroy(); instead of disconnect - not sure if this is going to cause me a problem long term, but it gets rid of this issue/bug

Finally got rid of this timeout spam in the console. Thank you! Works great for me. I make a disconnect and then client destroy.

            await this.client.disconnect();
            await this.client.destroy();

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants