Closed Atlas974 closed 7 months ago
What are BOT_ASYNC
and BOT_ASYNC_POOLSIZE
set to in the configuration?
What are
BOT_ASYNC
andBOT_ASYNC_POOLSIZE
set to in the configuration?
I'm using the default values:
I'm unable to reproduce this problem running errbot in a virtualenv
I tried BOT_ASYNC
as true and false, BOT_ASYNC_POOLSIZE
set 1, 5, 10 and 20.
errbot -v
Errbot version 6.1.8
lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 8.5.2111
Release: 8.5.2111
Codename: n/a
python --version
Python 3.8.8
pip freeze | grep matter
mattermostdriver==7.3.2
mattermost backend commit 38dd066e5a95495698eb51f5969d73ad3c554b78
bin/mattermost version
Version: 6.5.0
Build Number: 6.5.0
Build Date: Tue Mar 15 15:36:47 UTC 2022
Build Hash: 7fff157bcf85b54d595e22262a66d7f28d4b5a68
Build Enterprise Ready: true
OK, I misread CentOS7 as CentOS8, I'll test using 7.
CentOS7 doesn't come with Python3.8 packaging, so I compiled from source and setup a virtualenv.
lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.
1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 7.9.2009 (Core)
Release: 7.9.2009
Codename: Core
errbot -v
Errbot version 6.1.8
python --version
Python 3.8.13
pip freeze | grep mattermost
mattermostdriver==7.3.2
I'm still unable to reproduce the errors you're seeing.
@Atlas974 This should be fixed in master. Could you try running from the master branch?
We've had several releases and no responses. closing.
Describe the bug The bot ThreadPool is closed while processing a command.
To Reproduce Not identified.
Expected behavior The bot ThreadPool should be running?
Environment (please complete the following information):
Additional context