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
I'm testing the lm_finetuning script on Kubernetes. The docker image is based on Dockerfile-GPU.
The script has been modified a little where I remove the import MLFlowLogger and also the use of it in the lm_finetuning method (so I'm not using the MLFlowLogger at all). I still use the logging.basicConfig(..) though so I still can see the infos during runtime.
However, when I run the script, I see this showed up almost after every INFO:
WARNING - farm.utils - Failed to log params: 'getpwuid(): uid not found: 1174'
I looked into farm.utils and the only part that will throw this message is inside the log_params method of MLFlowLogger.
I didn't use the MLFlowLogger at all, why do I get this warning? How to solve this problem?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hi @lingsond, thank you for raising the issue. In the current version, an MLFlowLogger instance is instantiated by default. With work in progress #305, there's a new StdoutLogger being added that'd allow logging params/metrics on the stdout.
I'm testing the lm_finetuning script on Kubernetes. The docker image is based on Dockerfile-GPU.
The script has been modified a little where I remove the import MLFlowLogger and also the use of it in the lm_finetuning method (so I'm not using the MLFlowLogger at all). I still use the logging.basicConfig(..) though so I still can see the infos during runtime.
However, when I run the script, I see this showed up almost after every INFO:
WARNING - farm.utils - Failed to log params: 'getpwuid(): uid not found: 1174'
I looked into farm.utils and the only part that will throw this message is inside the log_params method of MLFlowLogger.
I didn't use the MLFlowLogger at all, why do I get this warning? How to solve this problem?
Thanks in advance.
The text was updated successfully, but these errors were encountered: