polettix / Bot-ChatBots-Telegram

Telegram adapter for Bot::ChatBots
Other
1 stars 0 forks source link

Can't start bot #11

Open Disinterpreter opened 3 years ago

Disinterpreter commented 3 years ago

Today my bot has fallen down and I can't start it again. When I try it i've got this error. I use longpoll. I didn't changes in the code since last season.

Mojo::Reactor::EV: I/O watcher failed: ERROR: code 400: Bad Request: chat not found at /usr/local/share/perl/5.24.1/WWW/Telegram/BotAPI.pm line 224.
    WWW::Telegram::BotAPI::api_request(undef, undef, HASH(0x55f93fface88)) called at /usr/local/share/perl/5.24.1/Bot/ChatBots/Telegram/Sender.pm line 92
    Bot::ChatBots::Telegram::Sender::send_message(undef, undef, "record", HASH(0x55f93fffd8c8)) called at /usr/local/share/perl/5.24.1/Bot/ChatBots/Telegram/LongPoll.pm line 125
    Bot::ChatBots::Telegram::LongPoll::__ANON__(Mojo::UserAgent=HASH(0x55f93f865700), Mojo::Transaction::HTTP=HASH(0x55f93ffaeed8)) called at /usr/local/share/perl/5.24.1/Mojo/UserAgent.pm line 252
    Mojo::UserAgent::_finish(Mojo::UserAgent=HASH(0x55f93f865700), "9590336480a944dfbb66d312cbeebfd5") called at /usr/local/share/perl/5.24.1/Mojo/UserAgent.pm line 279
    Mojo::UserAgent::_read(Mojo::UserAgent=HASH(0x55f93f865700), "9590336480a944dfbb66d312cbeebfd5", "HTTP/1.1 200 OK\x{d}\x{a}Server: nginx/1.16.1\x{d}\x{a}Date: Tue, 16 Mar 2021"...) called at /usr/local/share/perl/5.24.1/Mojo/UserAgent.pm line 134
    Mojo::UserAgent::__ANON__(Mojo::IOLoop::Stream=HASH(0x55f93ffacfc0)) called at /usr/local/share/perl/5.24.1/Mojo/EventEmitter.pm line 15
    Mojo::EventEmitter::emit(Mojo::IOLoop::Stream=HASH(0x55f93ffacfc0), "read", "HTTP/1.1 200 OK\x{d}\x{a}Server: nginx/1.16.1\x{d}\x{a}Date: Tue, 16 Mar 2021"...) called at /usr/local/share/perl/5.24.1/Mojo/IOLoop/Stream.pm line 110
    Mojo::IOLoop::Stream::_read(Mojo::IOLoop::Stream=HASH(0x55f93ffacfc0)) called at /usr/local/share/perl/5.24.1/Mojo/IOLoop/Stream.pm line 58
    Mojo::IOLoop::Stream::__ANON__(Mojo::Reactor::EV=HASH(0x55f93f4e7760)) called at /usr/local/share/perl/5.24.1/Mojo/Reactor/Poll.pm line 145
    eval {...} called at /usr/local/share/perl/5.24.1/Mojo/Reactor/Poll.pm line 145
    Mojo::Reactor::Poll::_try(Mojo::Reactor::EV=HASH(0x55f93f4e7760), "I/O watcher", CODE(0x55f93ffd2a28), 0) called at /usr/local/share/perl/5.24.1/Mojo/Reactor/EV.pm line 52
    Mojo::Reactor::EV::__ANON__(EV::IO=SCALAR(0x55f93ffd2e78), 1) called at /usr/local/share/perl/5.24.1/Mojo/Reactor/EV.pm line 30
    eval {...} called at /usr/local/share/perl/5.24.1/Mojo/Reactor/EV.pm line 30
    Mojo::Reactor::EV::start(Mojo::Reactor::EV=HASH(0x55f93f4e7760)) called at /usr/local/share/perl/5.24.1/Mojo/IOLoop.pm line 134
    Mojo::IOLoop::start("Mojo::IOLoop") called at /usr/local/share/perl/5.24.1/Bot/ChatBots/Telegram/LongPoll.pm line 153
    Bot::ChatBots::Telegram::LongPoll::start(Bot::ChatBots::Telegram::LongPoll=HASH(0x55f93f844038)) called at /usr/local/share/perl/5.24.1/Bot/ChatBots/Telegram/LongPoll.pm line 48
    Bot::ChatBots::Telegram::LongPoll::BUILD(Bot::ChatBots::Telegram::LongPoll=HASH(0x55f93f844038), HASH(0x55f93f9162e0)) called at (eval 60) line 80
polettix commented 3 years ago

From what I can see, it seems that there was either a change on the Telegram side or the specific chat disappeared:

ERROR: code 400: Bad Request: chat not found

Also, note that the error was actually raised by WWW::Telegram::BotAPI, which is used to manage the actual interactions at the API level.

Disinterpreter commented 3 years ago

From what I can see, it seems that there was either a change on the Telegram side or the specific chat disappeared:

ERROR: code 400: Bad Request: chat not found

Also, note that the error was actually raised by WWW::Telegram::BotAPI, which is used to manage the actual interactions at the API level.

the specific chat didn't disappeared because it must be reply to me and other people in DM. I think something was changed in Telegram side.

Yeah. I think I should make an issue in WWW::Telegram::BotAPI and link it to here.