Closed MajesticThrust closed 1 year ago
I think this is related to #405, and was at least somewhat addressed in de891a642801a4bd5bbb85b15b40a90233179780.
Switching to 01cdfd20354a0061925014c77b3e4680509cd68a fixed the issue.
I followed the instructions downloading promnesia via pip3 on macos today and I get the same error. Was the fix not propagated to the pip package? Is there a better way that I should be getting promnesia for that matter? As the Python package is also causing other issues.
I've been trying to get promnesia running on OS X, but once I get backend running, I get the following error on any page visit:
Happens both when I follow instructions in README.md (installing latest version with pip3), and also when running with Docker and custom
docker-compose.yaml
(pretty much identical todocker/docker_files/docker-compose.yaml
). Version1.2.20230515
in both cases.Not sure what's going on there. Could't find any mention of this in any of the previous issues. But I've noticed that the project doesn't appear to have any version locking for the dependencies. Could it be some sneaky change in some package that's causing this?