PosixPath object has no attribute endswith Win11 WSL2 about gptq-for-llama

[mpah]

same on google colab

[thulle]

diff --git a/llama.py b/llama.py
index 09b527e..cc652dd 100644
--- a/llama.py
+++ b/llama.py
@@ -238,7 +238,7 @@ def load_quant(model, checkpoint, wbits):
     make_quant(model, layers, wbits)
 
     print('Loading model ...')
-    if checkpoint.endswith('.safetensors'):
+    if checkpoint.as_posix().endswith('.safetensors'):
         from safetensors.torch import load_file as safe_load
         model.load_state_dict(safe_load(checkpoint))
     else:

that patch worked for me in linux at least

[aaronsantiago]

Same on windows native. A similar solution worked for me (skipping that check entirely).

[qwopqwop200]

Fixed a bug.
Please test if you still have such problem.
I didn't encounter such problem with wsl2.

[TheTerrasque]

I can confirm the same problem with current code:

text-generation-webui-text-generation-webui-1  | Loading llama-13b...
text-generation-webui-text-generation-webui-1  | Loading model ...
text-generation-webui-text-generation-webui-1  | Traceback (most recent call last):
text-generation-webui-text-generation-webui-1  |   File "/app/server.py", line 194, in <module>
text-generation-webui-text-generation-webui-1  |     shared.model, shared.tokenizer = load_model(shared.model_name)
text-generation-webui-text-generation-webui-1  |   File "/app/modules/models.py", line 119, in load_model
text-generation-webui-text-generation-webui-1  |     model = load_quant(path_to_model, Path(f"models/{pt_model}"), 4)
text-generation-webui-text-generation-webui-1  |   File "/app/repositories/GPTQ-for-LLaMa/llama.py", line 241, in load_quant
text-generation-webui-text-generation-webui-1  |     if checkpoint.endswith('.safetensors'):
text-generation-webui-text-generation-webui-1  | AttributeError: 'PosixPath' object has no attribute 'endswith'

Docker under Windows, python 3.10

Edit: on a side note, this might be connected to the python version

Edit2: After a rebuild now, I can't reproduce the error. Not sure what happened, it could be possible docker used an old build cache, but I don't see how. That layer have only started working due to changes done today which should invalidate all old layer caches.