Add a system to re-send and handle messages that fail to send #26
Labels
Milestone
Comments
|
One thing to note is that this bot is currently hosted on an Azure instance and if keepalives aren't being sent, a TCP connection will be dropped - at least I've noticed I had to configure ssh to send keepalives to keep my sessions alive when idle. (Although I do notice that keepalives are being established with discord so nvm that.) |
|
Running 6eb61c0 |
|
|
|
Doesn't work when I run |
|
Probably needs to be |
|
So I haven't had a time yet recently where I have both dumcord and IRC open, but I decided to take a look in the log and see if I could find it. And I did find one. So in this case the two messages that never made it to dumcord from IRC were:
The last message in this snippet from IRC ("where's ur arenas") did make it though, as well as the dumcord messages -> IRC. |
|
Config for reference. I'm not using any webhooks. # Dis4IRC Configuration File
# A list of bridges that Dis4IRC should start up
# Each bridge can bridge multiple channels between a single IRC and Discord Server
bridges {
# A bridge is a single bridged connection operating in its own space away from all the other bridges
# Most people will only need this one default bridge
default {
announce-joins-and-quits=false
# Mappings are the channel <-> channel bridging configurations
channel-mappings {
"341448913200349203"="#MLG"
"420114396313026560"="#griefprevention"
"420118648418467840"="#robomwm"
"341451241521545218"="#techfortress"
}
# Your discord API key you registered your bot with
discord-api-key="REDACTED"
# Configuration for connecting to the IRC server
irc {
allow-invalid-ssl-certs=false
anti-ping=true
# A list of __raw__ irc messages to send
init-commands-list=[
"PRIVMSG NICKSERV info",
"PRIVMSG NICKSERV help"
]
nickname=Dumcord
# Messages that match this regular expression will be passed to IRC without a user prefix
no-prefix-regex=null
port="6697"
realname=dum
server="irc.spi.gt"
use-ssl=true
username=cord
}
}
}
debug-logging=true |
|
That's just Discord API being garbage. Or your connection to it I suppose. I suppose we can investigate adding some system for making sure messages send and attempting to resend if they fail. |
zachbr
added
type: feature
|
@jamierocks just tried that command now, and that doesn't work because it tries to execute a file that's named as such in the doublequotes. |
zachbr
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a way to have it log to a file? My screen got messed up when I was copying in putty somehow so I took screenshots before I had to end up zapping it with commands outside of it.
It did this for two consecutive messages, the last messages before that were sent (from IRC) a few minutes ago. If my screen didn't get screwed up I would've seen if it could resolve itself. But yea logging to a file would be good unless there's a way to pipe to file and console.
The text was updated successfully, but these errors were encountered: