Ticket #236 (new defect)

Opened 2 years ago

Last modified 7 months ago

SmartShutDown locks HubBot thread

Reported by: dugwyler Owned by:
Priority: high Component: Core
Version: Latest version from repository Severity: critical
Keywords: Cc:

Description

It appears that after !smartshutdown is executed on a hub, the hub won't respond to any other commands until all idle bots have been shut down and it's essentially ready to log off. After this time all messages are processed: both incoming messages (it responds to your commands) and outgoing (it spams the bot debug chat with all of the bot death messages).

It would be nice if it didn't do this so that !listbots could be used to see which bots remain.

Attachments

Change History

Changed 2 years ago by milosh

  • owner set to nobody

Going for consistency.

Changed 13 months ago by Maverick

  • owner nobody deleted

Changed 13 months ago by Maverick

  • priority changed from normal to high
  • severity changed from minor to critical

This problem is related to the time it takes for a bot to be removed after doing !remove on the hub.
Some time ago a bot would log off in a few seconds, now the hub waits for the bot to be completely removed and even garbage collected before it proceeds operation.

This problem requires some priority.

Changed 7 months ago by Maverick

Related ticket #470.

Add/Change #236 (SmartShutDown locks HubBot thread)

Author


E-mail address and user name can be saved in the Preferences.


Action
as new
 
Note: See TracTickets for help on using tickets.