XthemeOrg / Xtheme

Xtheme IRC Services (a feature-packed, modern fork of atheme IRC Services)
https://github.com/XthemeOrg/Xtheme
Other
19 stars 8 forks source link

ChanServ help flags - slow to respond #61

Closed Casey952 closed 8 years ago

Casey952 commented 8 years ago

When doing ChanServ help flags - it is slow to respond. It brings up half the help file and then waits for a minute or longer and does the rest.

All other help commands are fine and displays them instantly.

on mIRC and Kiwi IRC, and checked with another user which is the same on their end.

-ChanServ- ***** ChanServ Help *****
-ChanServ- Help for FLAGS:
-ChanServ-  
-ChanServ- The FLAGS command allows for the granting/removal of channel
-ChanServ- privileges on a more specific, non-generalized level. It
-ChanServ- supports nicknames, groups and hostmasks as targets.
-ChanServ-  
-ChanServ- When only the channel argument is given, a listing of
-ChanServ- permissions granted to users will be displayed.
-ChanServ-  
-ChanServ- Syntax: FLAGS <#channel>
-ChanServ-  
-ChanServ- Otherwise, an access entry is modified. A modification may be
-ChanServ- specified by a template name (changes the access to the
-ChanServ- template) or a flags change (starts with + or -). See the
-ChanServ- TEMPLATE help entry for more information about templates.
-ChanServ-  
-ChanServ- If you are not a founder, you may only manipulate flags you
-ChanServ- have yourself, and may not edit users that have flags you
-ChanServ- don't have. For this purpose, +v grants the ability to grant
-ChanServ- +V, +o grants the ability to grant +O, and +r grants the
-ChanServ- ability to grant +b.
-ChanServ-  
-ChanServ- If the LIMITFLAGS option is set for the channel, this is
-ChanServ- restricted further, see help for SET LIMITFLAGS.
-ChanServ-  
-ChanServ-  
-ChanServ-  
-ChanServ- If you do not have +f you may still remove your own access
-ChanServ- with -*.
-ChanServ-  
-ChanServ- Syntax: FLAGS <#channel> [nickname|hostmask|group template]

waits for a minute or longer

-ChanServ- Syntax: FLAGS <#channel> [nickname|hostmask|group flag_changes]
-ChanServ-  
-ChanServ- Permissions:
-ChanServ-     +v - Enables use of the voice/devoice commands.
-ChanServ-     +V - Enables automatic voice.
-ChanServ-     +o - Enables use of the op/deop commands.
-ChanServ-     +O - Enables automatic op.
-ChanServ-     +s - Enables use of the set command.
-ChanServ-     +i - Enables use of the invite and getkey commands.
-ChanServ-     +r - Enables use of the kick, kickban, ban and unban commands.
-ChanServ-     +R - Enables use of the recover, sync and clear commands.
-ChanServ-     +f - Enables modification of channel access lists.
-ChanServ-     +t - Enables use of the topic and topicappend commands.
-ChanServ-     +A - Enables viewing of channel access lists.
-ChanServ-     +F - Grants full founder access.
-ChanServ-     +b - Enables automatic kickban.
-ChanServ-     +P - Suspends the user of any access or privileges.
-ChanServ-     +e - Exempts from +b and enables unbanning self.
-ChanServ-  
-ChanServ- The special permission +* adds all permissions except +b, +P and +F.
-ChanServ- ***** End of Help *****
siniStar7 commented 8 years ago

Can you provide details about which version of Xtheme, your IRCd and version? I will look into this shortly, but the above requested details would be of helpful information.

siniStar7 commented 8 years ago

I have tested for this in the latest git version, using InspIRCd-2.0.23 and could not replicate the problem you are describing.

This may be related to flood protection settings within your client, since this is a lot of output being given all at once.

Everything responded and displayed output within 1 second to me using /msg ChanServ HELP FLAGS.

Casey952 commented 8 years ago

Xtheme 7.4.2 Charybdis 3.5.0-rc1

siniStar7 commented 8 years ago

I also attempted to replicate the issue via Kiwi IRC, but still could not replicate the issue. Closing as this seems to be either host related, or client flood protection, rate-limiting by ircd, etc., but does not affect all clients/users.
If any other Charybdis users are experiencing this issue, please feel free to re-open and comment. (Otherwise, I will attempt to setup a Charybdis test-net later this week or next week to see if I can then replicate the issue)