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

Chat is not starting #12

Open
alex-aparin opened this issue Jan 24, 2025 · 2 comments
Open

Chat is not starting #12

alex-aparin opened this issue Jan 24, 2025 · 2 comments

Comments

@alex-aparin
Copy link

alex-aparin commented Jan 24, 2025

Hello. Thank you for interesting project. I decided to try it out, but the core container chat-backend is not starting.
Here is my steps to reproduce on master with SHA 69db040 (I skipped configuration step):
make network make build-up

Container is failed to start due missing uvicorn executable. I did not go into deep inspection of dockerfile, but it seems like needed packages are missing in container. Here is list of pip packages installed within container:

`Package Version


attrs 24.3.0
build 0.10.0
CacheControl 0.12.14
certifi 2024.12.14
cffi 1.17.1
charset-normalizer 3.4.1
cleo 2.1.0
crashtest 0.4.1
cryptography 44.0.0
distlib 0.3.9
dulwich 0.21.7
filelock 3.17.0
html5lib 1.1
idna 3.10
importlib_metadata 8.6.1
installer 0.7.0
jaraco.classes 3.4.0
jeepney 0.8.0
jsonschema 4.23.0
jsonschema-specifications 2024.10.1
keyring 23.13.1
lockfile 0.12.2
more-itertools 10.6.0
msgpack 1.1.0
packaging 24.2
pexpect 4.9.0
pip 23.2.1
pkginfo 1.12.0
platformdirs 3.11.0
poetry 1.5.1
poetry-core 1.6.1
poetry-plugin-export 1.5.0
ptyprocess 0.7.0
pycparser 2.22
pyproject_hooks 1.2.0
RapidFuzz 3.11.0
referencing 0.36.1
requests 2.32.3
requests-toolbelt 1.0.0
rpds-py 0.22.3
SecretStorage 3.3.3
setuptools 65.5.1
shellingham 1.5.4
six 1.17.0
tomlkit 0.13.2
trove-classifiers 2025.1.15.22
typing_extensions 4.12.2
urllib3 1.26.20
virtualenv 20.29.1
webencodings 0.5.1
wheel 0.42.0
zipp 3.21.0
`

@alex-aparin
Copy link
Author

UPD: dependencies were ignored due different python versions during pip installation, I changed python image version to fix it

@notarious2
Copy link
Owner

@alex-aparin If I remember correctly, the reason I've made different python versions in DockerFile and pyproject.toml is that Heroku's deployer didn't support latest python version. Sorry for inconvinience. I guess poetry would have raised an error if you've used it. Anyway, good that you've figured it out.

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

2 participants