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
The error indicates that the model_config property does not exist in the RLConfig class. After checking the RLConfig class and its parent class, GlobalConfig, I confirmed that model_config is not defined. Instead, there is a property called model_bump.
To make it work, I modified the source code as follows:
Replaced config.model_config() with config.model_bump.
Removed the parentheses, as model_bump appears to be a dictionary and not callable.
After these changes, the code worked as expected. However, I would like to confirm:
Are these modifications correct, or is there another intended way to resolve this issue?
Thanks in advance for your clarification and support!
The text was updated successfully, but these errors were encountered:
many thanks for your interest in REINVENT and welcome to the community!
write_config() is called at four different places, the four runmodes, in version 4.4.22. In all cases the content of config.model_dump() is passed to the function. I do not know where you believe the line you quoted to be located in the code. It would also be good to provide actual error messages to be able to track down a problem.
model_config is a class attribute in GlobalConfig used to configure a pydantic BaseModel.
Hi! First of all, many thanks for this amazing tool! 😊
I encountered an issue with Reinvent 4.4.22. When I run the reinvent command, an error occurs that points to the following lines in the code:
The error indicates that the model_config property does not exist in the RLConfig class. After checking the RLConfig class and its parent class, GlobalConfig, I confirmed that model_config is not defined. Instead, there is a property called model_bump.
To make it work, I modified the source code as follows:
After these changes, the code worked as expected. However, I would like to confirm:
Thanks in advance for your clarification and support!
The text was updated successfully, but these errors were encountered: