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
Make job_results give the same response as job_status when there are no results to report (e.g. because the job has not finished). A neat thing about this approach is that when you're polling for progress and get a response that the test has terminated, you're getting the results included that same response and you don't have to make an extra call to get the actual results.
On the other hand, if you have started a batch you might just want to know the progress, and not the result. If I understand the proposal, I think the solution today is cleaner.
If you just want to know the status of a job it's probably better to call job_status. This issue is about making job_results give better responses. It is not about removing job_status.
I see, it was the other way around. Well, that should not hurt anything. It just means that progress is included and result is empty until progress is 100. And error is not reported.
Make
job_results
give the same response asjob_status
when there are no results to report (e.g. because the job has not finished). A neat thing about this approach is that when you're polling for progress and get a response that the test has terminated, you're getting the results included that same response and you don't have to make an extra call to get the actual results.Stabilization
Tracking issue
Affected interfaces
Compatibly changed:
Dependencies
Overlapping proposals
None
The text was updated successfully, but these errors were encountered: