You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm working on dbrx to support GGUF architecture(#33260). ggml.py has been modified for this purpose, but I'm encountering the following error: "TypeError: expected str, bytes or os.PathLike object, not NoneType".
It seems the error is caused by gguf_checkpoint_path being defined as None in the load_gguf_checkpoint function in modeling_gguf_pytorch_utils.py. I'm currently tracking down why it is being set to NoneType.
Upon investigation, I found that the value is being passed as NoneType at line 2441 in tokenization_utils_base.py. I need to understand why this value, which previously worked correctly, is now being set to NoneType and address this issue.
try:
tokenizer=cls(*init_inputs, **init_kwargs)
It seems that the initial value for the GGUF file is being set to NoneType.
System Info
transformers
version: 4.46.0.dev0Who can help?
No response
Information
Tasks
examples
folder (such as GLUE/SQuAD, ...)Reproduction
Check it in Colab
Draft Code #33977
Expected behavior
Hi, I'm working on dbrx to support GGUF architecture(#33260).
ggml.py
has been modified for this purpose, but I'm encountering the following error: "TypeError: expected str, bytes or os.PathLike object, not NoneType".It seems the error is caused by
gguf_checkpoint_path
being defined asNone
in theload_gguf_checkpoint
function inmodeling_gguf_pytorch_utils.py
. I'm currently tracking down why it is being set toNoneType
.Upon investigation, I found that the value is being passed as
NoneType
at line 2441 intokenization_utils_base.py
. I need to understand why this value, which previously worked correctly, is now being set toNoneType
and address this issue.It seems that the initial value for the GGUF file is being set to
NoneType
.Here's the code for reference: Check it in Colab
Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: