-
Notifications
You must be signed in to change notification settings - Fork 1
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
Does not log channel messages with znc 1.7 #6
Comments
After lots and lots of debugging (which I find pretty hard, because as it seems python does not print errors anywhere when used in znc modules), I found out that changing Line 100 in 5542aa5
fixes this. God knows why. Actually, removing |
I've had the same experience debugging, it's really annoying to find out what's wrong, so usually I just wrap it with a try-catch and output the exception with I prefer staying on LTS-releases of Ubuntu and haven't upgraded to 18.04 yet so my ZNC is still on 1.6.3 and after upgrading I still wont have 1.7.0+ until another 2 years, so it will be a long time before I can debug this :) But there seems to have been a change in ZNC where it returns an signed char instead of unsigned char: znc/znc@a2470b3#diff-1d7bbb426d52e7e9fcfdf2eaa18e702a So maybe if we check the value against if realUser.GetPermChar() == 0:
return None
else:
return chr(realUser.GetPermChar()) |
I am on 16.04 LTS too, but for some reason, I didn't install znc from distro packages but added teward's ppa (I believe on the previous OS version I had (14.04 LTS maybe), znc was too old for my taste, hence the ppa). See https://wiki.znc.in/Installation#Install_via_PPA I might try your proposed fix some day :) |
ZNC 1.7 recently became stable, and because I am using teward's ubuntu PPA, I suddenly had upgraded from 1.6.3 without really knowing.
Ever since, channel messages aren't being logged anymore. Actions are, and I also see joins, quits and other things. I tried to debug this, but I just couldn't find out what's wrong. I don't get any errors.
The text was updated successfully, but these errors were encountered: