@@ -71,8 +71,8 @@ async def create_new_radix_job(job_component_name: str, job_scheduler_port: int)
71
71
LOGGER .error (f"Request returned HTTP error { exc .response .status_code } for POST to { exc .request .url !r} " )
72
72
return None
73
73
74
- # According to doc it seems we should be getting a json back that contains a status field,
75
- # which should be "Running" if the job was started successfully.
74
+ # According to the docs it seems we should be getting a json back that contains a
75
+ # status field, which should be "Running" if the job was started successfully.
76
76
# Apparently this is not the case, as of Feb 2024, the only useful piece of information we're getting
77
77
# back from this call is the name of the newly created job.
78
78
response_dict = response .json ()
@@ -93,11 +93,13 @@ async def get_radix_job_state(job_component_name: str, job_scheduler_port: int,
93
93
response = await client .get (url = url )
94
94
response .raise_for_status ()
95
95
96
- # LOGGER.debug("------")
97
- # response_dict = response.json()
98
- # LOGGER.debug(f"{response_dict=}")
99
- # LOGGER.debug("------")
96
+ LOGGER .debug ("------" )
97
+ response_dict = response .json ()
98
+ LOGGER .debug (f"{ response_dict = } " )
99
+ LOGGER .debug ("------" )
100
100
101
+ # Have a suspicion that the may not alwqys contain an entry for status
102
+ # This must be verified, but if that is the case, we must re-assess the RadixJobState pydantic model.
101
103
radix_job_state = RadixJobState .model_validate_json (response .content )
102
104
return radix_job_state
103
105
0 commit comments