关于finetune训练时提示no attribute 'MossTokenizer'、'MossConfig'、'MossForCausalLM'
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12.3k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
大神们好。最近在finetune训练的时候,经常会提示下面的这些错误:
报错1:
Traceback (most recent call last):
File "finetune_moss.py", line 305, in <module>
train(args)
File "finetune_moss.py", line 177, in train
tokenizer = AutoTokenizer.from_pretrained(args.model_name_or_path, trust_remote_code=True)
File "/root/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/models/auto/tokenization_auto.py", line 626, in from_pretrained
tokenizer_class = get_class_from_dynamic_module(
File "/root/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/dynamic_module_utils.py", line 374, in get_class_from_dynamic_module
return get_class_in_module(class_name, final_module.replace(".py", ""))
File "/root/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/dynamic_module_utils.py", line 148, in get_class_in_module
return getattr(module, class_name)
AttributeError: module 'transformers_modules.local.tokenization_moss' has no attribute 'MossTokenizer'
报错2:
Traceback (most recent call last):
File "finetune_moss.py", line 305, in <module>
train(args)
File "finetune_moss.py", line 180, in train
model = AutoModelForCausalLM.from_pretrained(args.model_name_or_path, trust_remote_code=True, use_cache=False)
File "/root/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/models/auto/auto_factory.py", line 434, in from_pretrained
config, kwargs = AutoConfig.from_pretrained(
File "/root/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/models/auto/configuration_auto.py", line 824, in from_pretrained
config_class = get_class_from_dynamic_module(
File "/root/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/dynamic_module_utils.py", line 374, in get_class_from_dynamic_module
return get_class_in_module(class_name, final_module.replace(".py", ""))
File "/root/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/dynamic_module_utils.py", line 148, in get_class_in_module
return getattr(module, class_name)
AttributeError: module 'transformers_modules.local.configuration_moss' has no attribute 'MossConfig'
报错3:
Traceback (most recent call last):
File "finetune_moss.py", line 305, in <module>
train(args)
File "finetune_moss.py", line 180, in train
model = AutoModelForCausalLM.from_pretrained(args.model_name_or_path, trust_remote_code=True, use_cache=False)
File "/root/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/models/auto/auto_factory.py", line 455, in from_pretrained
model_class = get_class_from_dynamic_module(
File "/root/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/dynamic_module_utils.py", line 374, in get_class_from_dynamic_module
return get_class_in_module(class_name, final_module.replace(".py", ""))
File "/root/anaconda3/envs/moss/lib/python3.8/site-packages/transformers/dynamic_module_utils.py", line 148, in get_class_in_module
return getattr(module, class_name)
AttributeError: module 'transformers_modules.local.modeling_moss' has no attribute 'MossForCausalLM'
这三个错误,每次都会随机有一个出现。请问是啥情况啊
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with finetune_moss.py around lines 177-180 and inspect the model_name_or_path contents used by AutoTokenizer and AutoModelForCausalLM. Compare the referenced local tokenization_moss.py, configuration_moss.py, and modeling_moss.py modules with the expected class names, then reproduce the failure and verify finetuning starts without any of the three missing-attribute errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100