Automattic / Automattic/wp-telegram-bot
Logs full with: Bad Request: chat not found
- Dominant language
- JavaScript
- Stars
- 17
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
```
2018-03-07T01:58:29.136066+00:00 app[web.1]: - Unhandled rejection Error: ETELEGRAM: 400 Bad Request: chat not found
2018-03-07T01:58:29.136088+00:00 app[web.1]: - at request.then.resp (/app/node_modules/node-telegram-bot-api/src/telegram.js:181:15)
2018-03-07T01:58:29.136091+00:00 app[web.1]: - at tryCatcher (/app/node_modules/bluebird/js/release/util.js:16:23)
2018-03-07T01:58:29.136092+00:00 app[web.1]: - at Promise._settlePromiseFromHandler (/app/node_modules/bluebird/js/release/promise.js:512:31)
2018-03-07T01:58:29.136094+00:00 app[web.1]: - at Promise._settlePromise (/app/node_modules/bluebird/js/release/promise.js:569:18)
2018-03-07T01:58:29.136095+00:00 app[web.1]: - at Promise._settlePromise0 (/app/node_modules/bluebird/js/release/promise.js:614:10)
2018-03-07T01:58:29.136097+00:00 app[web.1]: - at Promise._settlePromises (/app/node_modules/bluebird/js/release/promise.js:693:18)
2018-03-07T01:58:29.136099+00:00 app[web.1]: - at Async._drainQueue (/app/node_modules/bluebird/js/release/async.js:133:16)
2018-03-07T01:58:29.136100+00:00 app[web.1]: - at Async._drainQueues (/app/node_modules/bluebird/js/release/async.js:143:10)
2018-03-07T01:58:29.136102+00:00 app[web.1]: - at Immediate.Async.drainQueues (/app/node_modules/bluebird/js/release/async.js:17:14)
2018-03-07T01:58:29.136105+00:00 app[web.1]: - at runCallback (timers.js:789:20)
2018-03-07T01:58:29.136107+00:00 app[web.1]: - at tryOnImmediate (timers.js:751:5)
2018-03-07T01:58:29.136109+00:00 app[web.1]: - at processImmediate [as _immediateCallback] (timers.js:722:5)
````
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue provides only a production stack trace, pointing into node-telegram-bot-api/src/telegram.js. Start by locating the application call that sends the invalid chat request and determine how its rejection should be handled; done requires a reproducible cause and a confirmed way to prevent the recurring unhandled error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100