henkIs there ever gonna happen anything about https://trac.gajim.org/ticket/7492 ? It’s rather annoying and I want to get rid of it one way or another …
Link Mauvehenk, what is the issue exactly, you’d prefer it to output those warnings on stderr?
henkLink Mauve, errrr, no? I’d prefer it if this issue did not create so much load that my system can barely do anything else. I also consider more than one message per second to be unnecessary spamming, and that’s way more than that …
henkor, well, you know, if the issue wasn’t there to begin with …
Link MauveReading the nbxmpp code, this warning is here when send() is called with nothing to send.
Link MauveBut huh, that really loads your system that much? Just by enabling warnings? :/
Link MauveTry setting the logging level to info or critical.
Link MauveHmm, Gajim never calls logging.basicConfig.
mathieuithere are other ways to setup logging than logging.basicConfig.
mathieuiespecially since basicConfig is really limited
henkYes, at least one core is at 100%. And you see what happens to STDOUT. This prevents me from running gajim via the menu because that would cause my ~/.xsession-errors to fill my homedirectory and thereby crash other stuff.
Link MauveAh, it does setLevel.
henki.e.: this issue is a major nuisance and kinda made me stop using jabber regularly. I don’t like that, so if I can’t find a solution soon, I’ll just have to switch clients /-:
Link Mauvehenk, in src/common/logging_helpers.py remplace both root_log.setLevel(logging.WARNING) to root_log.setLevel(logging.CRITICAL).
henkLink Mauve, That might help, but it’s a workaround for my situation, while I need a solution.
Link MauveSure, but I’d like to know if your issue comes from logging itself or some other problem.
henkLink Mauve, Sorry, I can’t help with that.
Link MauveWell, try this change, and then report if it improved anything. ^^
mathieuiyes, since the warning only appears if an empty send() was done, the worrying thing is that it seems to be called thousand times a second
Link MauveYeah.
henkLink Mauve, ok, will do when I find the time, which might be some time around 2024 considering how it’s going right now.
Link Mauve^^'
Holgerhenk: So you won't have time to edit two lines for the next decade, while at the same time complaining that people haven't fixed your issue yet? ;-)
henkHolger, oh, sorry, did I complain about people? I actually only wanted to complain about the issue and try to find a solution without having to invest any time. Because I have no time ATM. I’m pissed by the bug and how it is handled. I’m sorry I don’t have >10 hours left to invest in a bug in a software I barely use or know. And I have already invested quite a few hours. Were I running gentoo, changing two lines would be something different, I guess, but I’m running debian and for a good reason. I’m not a dev and I’m not interested in wasting an hour just to get a build env for gajim running. Sorry, I just don’t have the time, especially not right now.
NathanYou literally need to spend two seconds to edit those lines
NathanWhat are you complaining about
henkNathan, About people who do not read, amongst other things. Read what I said and where I’d probably have to invest an hour or more. Also: You don’t know my life, so please don’t judge me.
Holgerhenk: So you're not only pissed by the bug but also by "how it is handled". I guess developers might just "don't have >10 hours left to invest in a bug" they haven't seen themselves, that's all.
Link Mauvehenk, Gajim is written in Python, no need to compile anything.
Link MauveJust open your text editor, modify those lines, and close/reopen Gajim.
Holgerhenk: And you can edit those lines as a Debian user in just the same way.
NathanHahaha when did I even mention anything about your life? It literally takes two seconds to edit those lines, not an hour or more.
Link MauveAlso, note that no Gajim developer is here right now.
HolgerYes, good point. I'm not affiliated with Gajim at all.
NathanJust for the record, me neither.
henkHolger, ok, and?
henkLink Mauve, Holger: ok, so I can do the changes in my system. Sorry, I did not know that. I thought I needed to rebuild it.
henkNathan, ^
henkThe problem is: I have no way to reproduce the issue, so this is not going to help at all …
Link MauveOh, this is bothersome.
Link MauveIs it related to a loss of connection, or a suspend, or something like that?
Link MauveBecause setting the logging levels to critical would make it so it won’t fill your ~/.xsession-errors, but not in any way fix the underlying issue.
henk'shrug' I have no idea … I’m suspecting a combination of suspend to ram, WLAN connection, and GPG.
henkack, it probably only fixes a symptom, not the problem …