-
Notifications
You must be signed in to change notification settings - Fork 34
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
telegram通知报错 #18
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
青龙部署的方式,qinglong 2.17.1 ,脚本成功运行完成后,发送telegram通知失败。(其他脚本如jdpro等能正常发送tg通知)
2024-02-28T15:13:20.924+0800 INFO 当前版本: 0.2.4
2024-02-28T15:13:20.924+0800 INFO 任务: youdao[false], 用户: doduo, 开始执行
2024-02-28T15:13:28.572+0800 INFO 当前登录状态为: {"login": true}
2024-02-28T15:13:31.751+0800 INFO doduo, 今天已经签到过了 {"callid": "f9bc3123-d5eb-45da-8eae-d2206d3eab5d"}
2024-02-28T15:13:31.756+0800 INFO cookie更新成功, youdao, doduo
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x99d6b7]
goroutine 1 [running]:
github.com/nikoksr/notify/service/telegram.(*Telegram).AddReceivers(...)
/Users/srcrs/Myself/go/pkg/mod/github.com/nikoksr/[email protected]/service/telegram/telegram.go:52
MagicTask/utils.HandlerSend({0xc000140870?, 0x53?}, {0xc0003ec220, 0x1e}, {0xc000040300, 0x22})
/Users/srcrs/Myself/MagicTask/utils/notify.go:34 +0x177
MagicTask/utils.HandlerFilterLoggerSend({0xc000140870, 0x41}, {0xc00013e900, 0x24}, {0xc0003ec220, 0x1e})
/Users/srcrs/Myself/MagicTask/utils/notify.go:160 +0x8a9
MagicTask/utils.Worker.func1()
/Users/srcrs/Myself/MagicTask/utils/utils.go:403 +0xdde
MagicTask/utils.Worker({0xae4fe9, 0x6}, {0xc0001194c6, 0x6})
/Users/srcrs/Myself/MagicTask/utils/utils.go:408 +0x1d9
MagicTask/tasks/youdao.(*Youdao).Run(0xae4fe9?, {0xc000234210?, 0xae4fe9?, 0x6?})
/Users/srcrs/Myself/MagicTask/tasks/youdao/run.go:40 +0x165
main.main()
/Users/srcrs/Myself/MagicTask/main.go:55 +0x4b3
执行结束... 耗时 41 秒
The text was updated successfully, but these errors were encountered: