-
Notifications
You must be signed in to change notification settings - Fork 43
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
Crash trying to delete #2
Comments
I see that the panic is pointing to the |
yep you are probably right, here the full conv with the bot: |
actually it is a bug, it's not about timing, it's just that |
what about just stop updating the old message if another one received? this will also allow to avoid update the message endless |
thank you! |
I just tried a "deldata 1" on an unmagnetized torrent (was shown with a red bar and with the hash in the web GUI) and i got this crash
panic: runtime error: index out of range
goroutine 202 [running]:
panic(0x667400, 0xc420012100)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
main.head(0x26b45191, 0xc420380000, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc4204460b0, 0x0, ...)
/root/go/src/github.com/pyed/transmission-telegram/transmission-telegram.go:434 +0xe92
created by main.main
/root/go/src/github.com/pyed/transmission-telegram/transmission-telegram.go:254 +0x78b
After a restart of the bin I got the message from the bot that the torrent was deleted with his data
The text was updated successfully, but these errors were encountered: