Open eliasdorneles opened 8 years ago
@eliasdorneles, my 2 cents:
It seems that HubStorage's /jobs/
endpoint no longer support scanning[1], so you probably want to use project.jobq.list()
instead. It'd be even better if you could use project.get_jobs()
, but it depends on what you need.
IMO we could ditch Jobs()
's list()
(or even the whole class, since it has only one method) or make a call to JobQ()
's list()
to keep compatibility and make it easier for applications currently using python-hubstorage. What do you think, @dangra?
@eliasdorneles, @bertinatto is correct. Lists on /jobs/
no longer works and /jobq/NN/list
should used instead. We can provide a semi backward compatible solution routing /jobs/NN/list to jobq/NN/list, the main difference is that not all job metadata is returned (you have to ask for the specific meta fields) and the order of the result changed. Most recent jobs are returned first.
According to service logs the projects using that api were already migrated, did I miss one?
Well, I had to fix a script that we run periodically.
@bertinatto +1 to updating hubstorage client library, but instead of removing the job I'd raise an exception with a nice message telling user the new way of doing things.
@eliasdorneles :+1:
Updated PR.
I'm getting bad request when using project.jobs.list():
Is this expected?