Custom Query (13624 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (19 - 21 of 13624)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Ticket Resolution Summary Owner Reporter
#11753 fixed Dvr/AddRecordSchedule does not work David Engel <dengel@…> robert.mcnamara@…
Description

The reworked AddRecordSchedule? does not work (and as near as I can tell never has). RecordingRule::isValid is called on the recording rule constructed, but the rule's start and end times and dates are never set. Thus, the duration will always be 0 and isValid will return false. Presumably adding (to Dvr::AddRecordSchedule?):

rule.m_startdate = recstartts.date(); rule.m_starttime = recstartts.time();

rule.m_enddate = recendts.date(); rule.m_endtime = recendts.time();

Will cause this to function as expected.

On an slightly related note, It's a serious bummer to have existing API calls reworked like this rather than replaced and the old ones deprecated-- anyone who has written a client against the existing API is in for a rude awakening when .27 is released.

#11773 fixed BE ocassionally reports DB Error (QueryAverageAspectRatio) David Engel <dengel@…> warpme@…
Description

Hi, 2 days ago I upgraded to current master and launch stress tests to test is system ready to production (series of 16x concurrent HD recordings, etc). Durring tests already I saw following error in BE log:

2013-08-23 11:15:01.030544 I  Finished recording 32 (Kuchnia+ HD) "2013-08-23 11:00:00": channel 21511
 2013-08-23 11:15:01.270309 E  DB Error (QueryAverageAspectRatio):
 Query was:
 SELECT recordedmarkup.type FROM recordedmarkup WHERE recordedmarkup.chanid    = ?    AND       recordedmarkup.starttime = ? AND       recordedmarkup.type      >= ? AND       recordedmarkup.type      <= ? GROUP BY recordedmarkup.type ORDER BY SUM( ( SELECT IFNULL(rm.mark, recordedmarkup.mark)                FROM recordedmarkup AS rm                 WHERE rm.chanid    = recordedmarkup.chanid    AND                       rm.starttime = recordedmarkup.starttime AND                       rm.type      = recordedmarkup.type      AND                       rm.mark      > recordedmarkup.mark                 ORDER BY rm.mark ASC LIMIT 1               ) - recordedmarkup.mark             ) DESC LIMIT 1
 Bindings were:
 :ASPECTEND=14, :ASPECTSTART=11, :CHANID=11110, :STARTTIME=2013-08-23T09:00:00Z
 No error type from QSqlError?  Strange...
 2013-08-23 11:15:01.270412 E  DB Error (QueryAverageAspectRatio):
 Query was:
 SELECT recordedmarkup.type FROM recordedmarkup WHERE recordedmarkup.chanid    = ?    AND       recordedmarkup.starttime = ? AND       recordedmarkup.type      >= ? AND       recordedmarkup.type      <= ? GROUP BY recordedmarkup.type ORDER BY SUM( ( SELECT IFNULL(rm.mark, recordedmarkup.mark)                FROM recordedmarkup AS rm                 WHERE rm.chanid    = recordedmarkup.chanid    AND                       rm.starttime = recordedmarkup.starttime AND                       rm.type      = recordedmarkup.type      AND                       rm.mark      > recordedmarkup.mark                 ORDER BY rm.mark ASC LIMIT 1               ) - recordedmarkup.mark             ) DESC LIMIT 1
 Bindings were:
 :ASPECTEND=14, :ASPECTSTART=11, :CHANID=11103, :STARTTIME=2013-08-23T09:00:00Z
 No error type from QSqlError?  Strange...
 2013-08-23 11:15:02.273076 I  Updating status for "46 (HBO Comedy HD)":"2013-08-23 11:00:00" on cardid 19 (Nagrywam => Nagrane)

I saw those errors independently on my stress tests but they are more frequent during tests. Full BE log attached.

#12605 fixed IPTV recorder consolidation during upgrade to master David Engel <dengel@…> charles.bovy@…
Description

Situation:

  • two single IPTV recorders
  • fixes/0.27 (db 1317)

After an upgrade to master, the two single IPTV recorders are consolidated into one IPTV recorder with multirec enabled (so still two recorders, but in same inputgroup). This consolidation is probably done before db upgrade to 1343.

Upgrade from 1342 to 1343 with two single IPTV recorders works perfect.

Relates to #12598

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Note: See TracQuery for help on using queries.