handle overly long messages properly #4

New Issue

jan6 · 2022-09-26T21:27:37Z

jan6 commented

2022-09-26 21:27:37 +00:00

while I do have "message too long" warning message implemented, there's no check for how much data we can ACTUALLY send
e.g. on libera, running 'exec mesg(dir(__import__("os"))) gives

00:20 <@bot6> message too long!
00:20 <@bot6> ['CLD_CONTINUED', 'CLD_DUMPED', 'CLD_EXITED', 'CLD_KILLED', 'CLD_STOPPED', 'CLD_TRAPPED', 'DirEntry', 'EX_CANTCREAT', 'EX_CONFIG', 'EX_DATAERR', 'EX_IOERR', 'EX_NOHOST', 'EX_NOINPUT', 'EX_NOPERM', 'EX_NOUSER', 'EX_OK', 'EX_OSERR', 'EX_OSFILE', 'EX_PROTOCOL', 'EX_SOFTWARE', 'EX_TEMPFAIL', 'EX_UNAVAILABLE', 'EX_USAGE', 'F_LOCK', 'F_OK', 'F_TEST', 'F_TLOCK', 'F_ULOCK', 'GRND_NONBLOCK', 'GRND_RANDOM', 'GenericAlias', 'MFD_ALLOW_SEALING', 'MFD_CLOEXEC', 'MFD_HUGETLB', 'MFD

basically just cuts the message short
but the same thing on ircnow (running ngircd), gives

00:21 <bot6> message too long!
00:21 <-- bot6 (~jan6_bot@6c062189) has quit (Request too long)

while I do have "message too long" warning message implemented, there's no check for how much data we can ACTUALLY send e.g. on libera, running `'exec mesg(dir(__import__("os")))` gives ``` 00:20 <@bot6> message too long! 00:20 <@bot6> ['CLD_CONTINUED', 'CLD_DUMPED', 'CLD_EXITED', 'CLD_KILLED', 'CLD_STOPPED', 'CLD_TRAPPED', 'DirEntry', 'EX_CANTCREAT', 'EX_CONFIG', 'EX_DATAERR', 'EX_IOERR', 'EX_NOHOST', 'EX_NOINPUT', 'EX_NOPERM', 'EX_NOUSER', 'EX_OK', 'EX_OSERR', 'EX_OSFILE', 'EX_PROTOCOL', 'EX_SOFTWARE', 'EX_TEMPFAIL', 'EX_UNAVAILABLE', 'EX_USAGE', 'F_LOCK', 'F_OK', 'F_TEST', 'F_TLOCK', 'F_ULOCK', 'GRND_NONBLOCK', 'GRND_RANDOM', 'GenericAlias', 'MFD_ALLOW_SEALING', 'MFD_CLOEXEC', 'MFD_HUGETLB', 'MFD ``` basically just cuts the message short but the same thing on ircnow (running ngircd), gives ``` 00:21 <bot6> message too long! 00:21 <-- bot6 (~jan6_bot@6c062189) has quit (Request too long) ```

jan6 closed this issue

2022-09-26 22:43:13 +00:00

Sign in to join this conversation.