Writing your own remote control commands Remote control commands are registered in the control panel and they take a single argu- ment: the current ControlDispatch instance. From there you have access connection: from celery.worker.control import Panel @Panel.register def reset_connection(panel): panel.logger.critical("Connection reset by remote control.") panel.listener.reset_connection() return {"ok": account. You need to create a GitHub account to be able to create new issues and participate in the discussion. 2. Determine if your bug is really a bug. You should not file a bug if you are requesting support

Writing your own remote control commands Remote control commands are registered in the control panel and they take a single argument: the current ControlDispatch instance. From there you have access connection: from celery.worker.control import Panel @Panel.register def reset_connection(panel): panel.logger.critical("Connection reset by remote control.") panel.listener.reset_connection() return account [https://github.com/signup/free] to be able to create new issues and participate in the discussion. 2. Determine if your bug is really a bug. You should not file a bug if you are requesting support

Writing your own remote control commands Remote control commands are registered in the control panel and they take a single argument: the current ControlDispatch instance. From there you have access connection: from celery.worker.control import Panel @Panel.register def reset_connection(panel): panel.logger.critical("Connection reset by remote control.") panel.consumer.reset_connection() return {"ok": account. You need to create a GitHub account to be able to create new issues and participate in the discussion. 2. Determine if your bug is really a bug. You should not file a bug if you are requesting support

Writing your own remote control commands Remote control commands are registered in the control panel and they take a single argument: the current ControlDispatch instance. From there you have access connection: from celery.worker.control import Panel @Panel.register def reset_connection(panel): panel.logger.critical("Connection reset by remote control.") panel.consumer.reset_connection() return {"ok": account. You need to create a GitHub account to be able to create new issues and participate in the discussion. 2. Determine if your bug is really a bug. You should not file a bug if you are requesting support

Writing your own remote control commands Remote control commands are registered in the control panel and they take a single argument: the current ControlDispatch instance. From there you have access connection: from celery.worker.control import Panel @Panel.register def reset_connection(panel): panel.logger.critical("Connection reset by remote control.") panel.consumer.reset_connection() return account [https://github.com/signup/free] to be able to create new issues and participate in the discussion. 2. Determine if your bug is really a bug. You should not file a bug if you are requesting support

Writing your own remote control commands Remote control commands are registered in the control panel and they take a single argument: the current ControlDispatch instance. From there you have access connection: from celery.worker.control import Panel @Panel.register def reset_connection(panel): panel.logger.critical("Connection reset by remote control.") panel.consumer.reset_connection() return account [https://github.com/signup/free] to be able to create new issues and participate in the discussion. 2. Determine if your bug is really a bug. You should not file a bug if you are requesting support

Writing your own remote control commands Remote control commands are registered in the control panel and they take a single argument: the current ControlDispatch instance. From there you have access connection: from celery.worker.control import Panel @Panel.register def reset_connection(panel): panel.logger.critical("Connection reset by remote control.") panel.consumer.reset_connection() return {"ok": account. You need to create a GitHub account to be able to create new issues and participate in the discussion. 2. Determine if your bug is really a bug. You should not file a bug if you are requesting support

Writing your own remote control commands Remote control commands are registered in the control panel and they take a single argument: the current ControlDispatch instance. From there you have access connection: from celery.worker.control import Panel @Panel.register def reset_connection(panel): panel.logger.critical("Connection reset by remote control.") panel.consumer.reset_connection() return {"ok": account. You need to create a GitHub account to be able to create new issues and participate in the discussion. 2. Determine if your bug is really a bug. You should not file a bug if you are requesting support

Writing your own remote control commands Remote control commands are registered in the control panel and they take a single argument: the current ControlDispatch instance. From there you have access connection: from celery.worker.control import Panel @Panel.register def reset_connection(panel): panel.logger.critical("Connection reset by remote control.") panel.consumer.reset_connection() return account [https://github.com/signup/free] to be able to create new issues and participate in the discussion. 2. Determine if your bug is really a bug. You should not file a bug if you are requesting support

Writing your own remote control commands Remote control commands are registered in the control panel and they take a single argument: the current ControlDispatch instance. From there you have access connection: from celery.worker.control import Panel @Panel.register def reset_connection(panel): panel.logger.critical("Connection reset by remote control.") panel.consumer.reset_connection() return account [https://github.com/signup/free] to be able to create new issues and participate in the discussion. 2. Determine if your bug is really a bug. You should not file a bug if you are requesting support