gaowanliang / gaowanliang/DownloadBot
无法正常运行
- Dominant language
- Go
- Stars
- 800
- Forks
- 200
- PR merge metrics
- No merged PRs in 30d
Description

使用Start或者转发文件就会崩溃
2023-02-22 03:14:09 INFO 服务器监听在 [::]:23369
2023-02-22 03:14:11 INFO 与 http://10.32.0.151:6800/jsonrpc 连接中
2023-02-22 03:14:11 INFO Aria2 websocket连接已建立!Aria2版本:1.36.0
2023-02-22 03:14:11 INFO 已登入授权账户 xx
2023-02-22 03:14:36 PANIC %!w(*tgbotapi.Error=&{400 Bad Request: can't parse entities: Can't find end of the entity starting at byte offset 10 {0 0}})
panic: %!w(*tgbotapi.Error=&{400 Bad Request: can't parse entities: Can't find end of the entity starting at byte offset 10 {0 0}})
goroutine 14 [running]:
go.uber.org/zap/zapcore.CheckWriteAction.OnWrite(0x0?, 0x0?, {0x0?, 0x0?, 0xc00038e2a0?})
D:/DownloadBot/vendor/go.uber.org/zap/zapcore/entry.go:198 +0x65
go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc000096340, {0x0, 0x0, 0x0})
D:/DownloadBot/vendor/go.uber.org/zap/zapcore/entry.go:264 +0x3ec
go.uber.org/zap.(*SugaredLogger).log(0xc00049fa90, 0x4, {0x8066e9?, 0x14e6e8?}, {0xc0004a06c0?, 0x80?, 0x78?}, {0x0, 0x0, 0x0})
D:/DownloadBot/vendor/go.uber.org/zap/sugar.go:295 +0xee
go.uber.org/zap.(*SugaredLogger).Panicf(...)
D:/DownloadBot/vendor/go.uber.org/zap/sugar.go:189
DownloadBot/tool/zap.Panic({0x8066e9?, 0x0?}, {0xc0004a06c0?, 0x0?, 0x0?})
D:/DownloadBot/tool/zap/zap.go:119 +0xb5
DownloadBot/tool/output/telegram.dropErr(...)
D:/DownloadBot/tool/output/telegram/telegram.go:36
DownloadBot/tool/output/telegram.Aria2Bot({0xc00002ef30, 0x2e}, 0xc0000ac270)
D:/DownloadBot/tool/output/telegram/telegram.go:488 +0x1d9d
created by main.main
D:/DownloadBot/cmd/DownloadBot/main.go:43 +0xd8
RPC地址可以正常使用

Contributor guide
No contributing guide indexed for this repository
Research direction
Start in tool/output/telegram/telegram.go around Aria2Bot at line 488 and inspect the error path through dropErr at line 36. Reproduce the crash using Start or file forwarding and compare the Telegram 400 entity-parsing error with the logged request; done means these actions no longer panic on the reported input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100