Remove old version of exllamav2 to use the same version on text-generation-webui #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
when merge ? when RunPod working again... when lambo ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to resolve #17 by removing the old version of exllamav2 and use the same version on text-generation-webui.
As of now when this PR created, the currently running version of exllamav2 on the template is 0.11 which breaks as text-generation-webui use version 0.15 which introduce Q4 cache mode. Hence we ran into #17 as the text-generation-webui class ExLlamaV2Cache_Q4 requires the Q4 cache mode from the new version of exllamav2 to work.