Bug 16671 - preset_data loop in playerstatus may have broken playerstatus updates for some players
: preset_data loop in playerstatus may have broken playerstatus updates for som...
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Misc
: 7.6.0
: PC Other
: P1 major (vote)
: 7.6.0
Assigned To: Ben Klaas
http://forums.slimdevices.com/showthr...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-18 13:07 UTC by Ben Klaas
Modified: 2011-05-09 09:36 UTC (History)
0 users

See Also:
Category: Bug


Attachments
do extra checking on presets data structure before populating presets_data loop (967 bytes, patch)
2010-11-18 13:14 UTC, Ben Klaas
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Klaas 2010-11-18 13:07:54 UTC
users in forum reporting that Now Playing window is showing just text of "Nothing" on screen after updating to 31538 from 31534. Reverting to 31534 fixes the issue.

Only candidate amongst those 4 checkins causing this failure is 31537, which adds preset_data loop to the playerstatus response generated from Slim::Queries::statusQuery().
Comment 1 Ben Klaas 2010-11-18 13:14:47 UTC
Created attachment 7042 [details]
do extra checking on presets data structure before populating presets_data loop

without reproducing the issue yet, this is a bit of a longshot, but this patch includes extra checking to make sure that $presets is an arrayref and each defined element in the array are hashrefs.
Comment 2 SVN Bot 2010-11-19 09:18:23 UTC
 == Auto-comment from SVN commit #31548 to the slim repo by bklaas ==
 == http://svn.slimdevices.com/slim?view=revision&revision=31548 ==

Bug: 16671
Description: check that the returned data structure for presets data is appropriate for sending out to the player
Comment 3 SVN Bot 2010-11-21 04:02:24 UTC
 == Auto-comment from SVN commit #31549 to the slim repo by adrian ==
 == http://svn.slimdevices.com/slim?view=revision&revision=31549 ==

Bug: 16671
Description: fix typo which causes this code to fail
Comment 4 Ben Klaas 2011-01-14 10:02:35 UTC
I think we're okay on this one now