mirror of
https://github.com/SillyTavern/SillyTavern-Extras.git
synced 2026-10-16 10:31:52 +00:00
[GH-ISSUE #183] changes to requirements-complete.txt to make it work #106
Labels
No labels
bug
duplicate
planned
pull-request
under consideration
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
SillyTavern/SillyTavern-Extras#106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @eyalgi11 on GitHub (Nov 12, 2023).
Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Extras/issues/183
i needed to change the default file to this to make this work
@Cohee1207 commented on GitHub (Nov 12, 2023):
So basically remove fixed versions, yeah?
@eyalgi11 commented on GitHub (Nov 13, 2023):
yea
@GoAwayNow commented on GitHub (Nov 16, 2023):
The conflict comes from TTS requiring numpy 1.22.0 exactly while some others require 1.22.5 minimum. Under python 3.10, TTS always requires 1.22.0, so this seems to result in older versions of some other packages being installed.
@Cohee1207 commented on GitHub (Nov 16, 2023):
I applied the change and split requirements into main/coqui/rvc.
completefile was removed@rosx27 commented on GitHub (Nov 16, 2023):
lib installation takes too long. but i hope this fixes the issue.
UPDATE:
due to module not found error, i specified the version of these two libraries:
from
sentence-transformerstosentence-transformers==2.2.1from
pypikatopypika==0.48.8note: i ignored "chromadb 0.4.17 requires pypika>=0.48.9, but you have pypika 0.48.8 which is incompatible."@rosx27 commented on GitHub (Nov 16, 2023):
i think the implementation of chromadb should also be updated, there is a new version of chromadb, i think the outdated implementation of this is the reason why i get this error:
also, there is error in rvc, coqui-tts:
docs points me here. i'm installing it right now, will try to update tomorrow it this fixes the error.
@Cohee1207 commented on GitHub (Nov 16, 2023):
You're right about chroma, that was the only module I didn't test after the update and it broke, the irony. Hopefully fixed now.
As for coqui and rvc, both worked for me. The expected order of requirements installation is the following:
requirements => rvc => coquiAnd coqui still sucks, at least as a package to work with, because all of these issues with pip requirements.
@rosx27 commented on GitHub (Nov 16, 2023):
that was quick. anyway, i'll pull your updates now and test it.
haha yeah? i've only used silero-server, never tried other tts yet. i was hoping to give it a try since i now have some time to tinker with tts due to work.
@GoAwayNow commented on GitHub (Nov 16, 2023):
Should ChromaDB be versioned in the requirements? The migration logs on the site are only a few months apart, there could be some risk of it making breaking changes again before long.
@rosx27 commented on GitHub (Nov 17, 2023):
i think so, since the changes were to address multi modal embeddings and I think that's a way to go, and the risk of revising, and possibly breaking the revised implementation due to another update in the future should be acceptable since the current implementation of chromadb is not working.
anyway, here's my update on the current commit [
51a6809]:the chroma API posts, however, retrieval via manual export of the json file or automatic retrieval is not working and giving me an error "chat history [---] not found." or something, I'll update this later when I get home.
EDIT:

thats the output i get when i click "export" under smart context
@GoAwayNow commented on GitHub (Nov 17, 2023):
So, I'm running in a modified version of the Colab with ChromaDB persistence via Google Drive, and the current commit + latest chromadb works fine for me. Notably, though, I got similar errors before extras was updated for the latest chromadb versions. Specifically, I got those errors because I ran with the new version of chromadb, and then tried to roll back to 0.4.10, but my chromadb.sqlite3 had been changed. This is actually why I was bringing up adding the version, because future changes could make it impossible for users to roll back.