Ticket #10540 (closed Bug Report - General: Fixed)
Opened 14 months ago
Last modified 14 months ago
Service API Dvr RemoveRecorded does not work
| Reported by: | cletus@… | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.25 |
| Component: | MythTV - General | Version: | Master Head |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
When calling ServiceAPI::Dvr::RemoveRecorded? mythtv's ServiceAPI needs StartTime? in MySQL ISO format, e.g.: curl -d 'ChanId?=34006&StartTime?=2012-03-30T17:00:00Z' 'http://192.168.1.99:6544/Dvr/RemoveRecorded'
The Service API translates it into an DELETE_RECORDING message and uses the ISO format StartTime? as parameter. However, DELETE_RECODRING needs datetime ( http://www.mythtv.org/wiki/DELETE_RECORDING_(Myth_Protocol) ) and thus DELETE_RECORDING fails:
HttpServer43 remoteutil.cpp:132 (RemoteDeleteRecording?) - Failed to delete recording 34006:2012-03-30T19:00:00
Attachments
Change History
comment:1 Changed 14 months ago by robertm
comment:2 Changed 14 months ago by robertm
Even once the API itself is fixed, the issue also appears to be that the reporter is providing input in localtime rather than UTC.
comment:3 Changed 14 months ago by robertm
- Status changed from new to closed
- Resolution set to Fixed
The above is an incorrect assessment-- all input to the Service API is returned to local time by the time it is processed in the business logic. UTC is not the issue with the API. The issue is that it calls remotedeleterecording, which is not possible as the backend would need to connect to itself to issue the command.