Hi UnevenDolphin73 ,
Thanks for bringing this to our attention!
BTW, there was no requirements change i the new agent version as far as I know, so perhaps this is simply a new requirement by poetry?
UnevenDolphin73 can you please check agent version v1.5.1rc0? This should fix the pip issue as well as the last error you've sent (basically a deprecated jsonschema usage issue that is now unsupported)
At least as far as I can tell, nothing else has changed on our systems. Previous
pip versions would warn about this, but not crash.
Hm, I did not specify any specific versions previously. What was the previous default?
SuccessfulKoala55 This is due to the
pip update in
Well, you can still limit the pip version in the configuration
Now I tried setting
pip version to
<22.3 (both in the
config and in the scaler's "extra config parameters"), but still it uses the latest?
added seed packages: pip==22.3.1, setuptools==65.5.1, wheel==0.38.4
SuccessfulKoala55 This happens pip >= 22.3 btw.
Another semi-related issue is that I now encounter these kind of error messages:
clearml_agent: ERROR: __init__() got an unexpected keyword argument 'types'
UnevenDolphin73 when do you encounter these errors? When running clearml-agent daemon? Or during task execution? Can you attach some log to provide context?
These issues popped when I upgraded to clearml-agent 1.5.0.
There's not much (or anything) in the log to provide...
` (.venv) 15:42 [0:user@server$~] CLEARML_CONFIG_FILE=~/agent_clearml.conf clearml-agent daemon --queue default on_prem --detached --order-fairness
Environment variables set from configuration: ['AWS_ACCESS_KEY_ID', 'AWS_SECRET_ACCESS_KEY', 'AWS_DEFAULT_REGION']
clearml_agent: ERROR: init() got an unexpected keyword argument 'types' `
Sorry for the late reply Jake -- I was away on holidays -- it works perfectly now, thanks!
The last kind when launching the agents.
The former on task execution.