Closed MattYoon closed 1 year ago
cc @ArthurZucker
Hey! Indeed one of our CI test is failing because of that. Looking into it now!
Yep, the issue is that in the CONFIG_MAPPING_NAMES
umt5
maps to mt5 (since they have the same configuration file). This is messing with the overall mapping. A custom coming has to be create, or find a way to properly update! 😉
Hmm. The values in CONFIG_MAPPING(_NAMES)
is used as keys when creating MODEL_MAPPING
. We should remove the entries of umt5
in CONFIG_MAPPING_NAMES
and other mappings.
Those models should be loaded in a non-auto way.
We can't just remove every mapping, some of our checks and doc require them. Let's just add a config for UMT5.
System Info
transformers
version: 4.31.0.dev0Who can help?
@ArthurZucker
Information
Tasks
examples
folder (such as GLUE/SQuAD, ...)Reproduction
Expected behavior
@ArthurZucker Thank you for the recent integration of umT5. However, from the latest branch of transformers, loading normal mT5 will load from UMT5 class. Of course this does not happen with 4.30.2.