Skip to content
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

Enabling the Q module requires sending messages to Q twice for output #554

Closed
Zarthus opened this issue May 18, 2014 · 1 comment
Closed
Assignees

Comments

@Zarthus
Copy link
Contributor

Zarthus commented May 18, 2014

Hey there, I've ran into an odd issue when the Q module is enabled.

You have to message Q twice to get output (for example, with msg q whoami)

This has been tested with mIRC 7.29, mIRC 7.32, irssi v0.8.15, on znc versions 1.2-3~precise0, and 1.2

To reproduce, simply connect to your bouncer, enable the Q module, and message Q any command. In my case, WHOAMI. You would have to message the bot twice to get a response. This seems to work in turns (once you receive the message, the next one won't be received).

For what it's worth, here is the mIRC debug logs.

-> blacklotus.ca.us.quakenet.org PRIVMSG q :whoami
-> blacklotus.ca.us.quakenet.org PRIVMSG q :whoami
<- :Q!TheQBot@CServe.quakenet.org NOTICE Zarthus :-Information for user Zarthus (using account BuuGhost):
[snipped personal data]
<- :Q!TheQBot@CServe.quakenet.org NOTICE Zarthus :End of list.

And normal IRC logs

(21:07:17) <-*status> Loaded module [q] [/usr/local/lib/znc/q.so]
(21:07:21) -> *q* whoami
(21:07:22) -Q- -Information for user Zarthus (using account BuuGhost):
...
(21:07:22) -Q- End of list.
(21:07:23) -> *q* whoami
(21:07:25) -> *q* whoami
(21:07:25) -Q- -Information for user Zarthus (using account BuuGhost):
...
(21:07:25) -Q- End of list.

Gist of znc in debug mode, it doesn't add a whole lot.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@Jay2k1
Copy link

Jay2k1 commented May 18, 2014

I have the same issue, running 1.2-3~precise0 and irssi 0.8.15. I noticed that the logfile of the conversation with Q receives the answers of Q even when the client does not. As it seems, every first command's responses get eaten, every thirds, fifths and so on.

Zarthus added a commit to Zarthus/znc that referenced this issue Apr 20, 2019
Q can be replaced with the perform module, and will still be available
as a third-party module for those who use the module and QuakeNet.

In general, the Q module only targets a single network not everyone may
use, the additional support and maintenance burden is not worth it.

References znc#786
Closes znc#1636 as wontfix
Closes znc#554 as wontfix
Zarthus added a commit to Zarthus/znc that referenced this issue Apr 20, 2019
Q can be replaced with the perform module, and will still be available
as a third-party module for those who use the module and QuakeNet.

In general, the Q module only targets a single network not everyone may
use, the additional support and maintenance burden is not worth it.

References znc#786
Closes znc#1636 as wontfix
Closes znc#554 as wontfix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants