smlindauer
commented
1 year ago I recreated this issue in v1.5.4 and found that the bug did not persist in the more recent releases of sasctl.
Upon further investigation, I discovered that this is a known issue from 1.5.4 caused by the usage of Viya 3.4's filter method (specifically using modelRepository/projects/?properties=(name,%20EVU_Iris3) in this example instead of modelRepository/projects?filter=eq(name,%20EVU_Iris3)). This was fixed in 9df0eee76456d3d35c4d7b414a833293e6da8ac9, which maps to sasctl version 1.7.3.
Upgrading to v1.7.3 will fix the error, however I would suggest upgrading to the most recent release of v1.9.1.
EdwinvanUnen
Describe the issue When registering a (first) model into a MM-project it creates the project in case it doesn't exist. But when I try to register a second model it fails because "the project is already in use". Note: the second model is succesfully put into the Public repository with new version, but not in the MM project.
To Reproduce This is the code: first creating the astore, then registering the model:
df.regression.logistic(target='Species', inputs=features, savestate={"caslib":'Casuser',"name":'iris_model_table',"Replace":'True'}) astore = sess.CASTable('iris_model_table') with Session(host, username='snlevu',password=password): model = register_model(astore, 'iris logistic3', 'EVU_Iris3', force=True)
Full Error:
HTTPError Traceback (most recent call last) /tmp/ipykernel_32401/2443453042.py in
1 with Session(host, username='snlevu',password=password):
----> 2 model = register_model(astore, 'iris logistic3', 'EVU_Iris3', force=True)
/opt/anaconda3/lib/python3.8/site-packages/sasctl/tasks.py in register_model(model, name, project, repository, input, version, files, force, record_packages) 299 model_props = {} 300 --> 301 project = _create_project(project, model_props, repo_obj, 302 invar, outvar) 303
/opt/anaconda3/lib/python3.8/site-packages/sasctl/tasks.py in _create_project(project_name, model, repo, input_vars, output_vars) 147 properties['targetLevel'] = None 148 --> 149 project = mr.create_project(project_name, repo, 150 variables=input_vars + output_vars, 151 **properties)
/opt/anaconda3/lib/python3.8/site-packages/sasctl/_services/model_repository.py in create_project(cls, project, repository, **kwargs) 436 437 project.update(kwargs) --> 438 return cls.post('/projects', json=project, 439 headers={ 440 'Content-Type':
/opt/anaconda3/lib/python3.8/site-packages/sasctl/_services/service.py in post(cls, *args, kwargs) 115 def post(cls, *args, *kwargs): 116 """Send a POST request.""" --> 117 return cls.request('post', args, kwargs) 118 119 @classmethod
/opt/anaconda3/lib/python3.8/site-packages/sasctl/_services/service.py in request(cls, verb, path, session, raw, format, kwargs) 95 path = cls._SERVICE_ROOT + '/' + path 96 ---> 97 return core.request(verb, path, session, raw, format, kwargs) 98 99 @classmethod
/opt/anaconda3/lib/python3.8/site-packages/sasctl/core.py in request(verb, path, session, raw, format, **kwargs) 1138 1139 if 400 <= response.status_code <= 599: -> 1140 raise HTTPError(response.url, response.status_code, response.text, 1141 response.headers, None) 1142
HTTPError: HTTP Error 409: {"version":2,"httpStatusCode":409,"errorCode":21201,"message":"The name \"EVU_Iris3\" is already in use within the selected folder. Enter a unique name.","details":["path: /modelRepository/projects","correlator: f5d79f76-60e3-44e1-83a6-b0a8360710b3"]}
Expected behavior I expect the system to add the second model in the Model Manager project EVU_Iris3. But it fails because it already exists. It puts the model correctly in the Public Repository with a new version nr.
** Viya-Server: https://viya401.zeus.sashq-d.openstack.sas.com/
Version SASCTL version: 1.5.4