Description of problem: there are a few areas in pulp return JSON that has date objects. was trying to figure out if this was epoch seconds but clearly is not: return date from sync status: call: /pulp/api/repositories/fedora-12333277/sync/69856efd-4669-11e0-b8a1-00219b3b5088/", return json: "start_time": { "$date": 1299229937723 } irb session: Time.at(1299229937723) => 43140-12-16 07:55:23 -0500 would suggest updating pulp docs to explain what date structure this is or send over scalar value as timestamp or epoch seconds. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Need to re-test, this might be working now.
We noted the date formats have changed in the sync status, now we get a much nicer: { ... "finish_time": "1300208938", "start_time": "1300208857", ... I think we can move this to ON_QA
verified [root@preethi ~]# rpm -q pulp pulp-0.0.154-1.fc14.noarch [root@preethi ~]# [root@preethi ~]# curl -k -u admin:admin https://localhost/pulp/api/repositories/f14/sync/ |json_reformat % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 813 0 813 0 0 2156 0 --:--:-- --:--:-- --:--:-- 2191 [ { "scheduled_time": 0, "exception": null, "status_path": "/pulp/api/repositories/f14/sync/8a01cc87-54c5-11e0-9621-002564a85a58/", "finish_time": "1300826950", "start_time": "1300826822", "traceback": null,
Closing with Community Release 15 pulp-0.0.223-4.