touch-packages team mailing list archive

[Marco Trevisan (Treviño) <mail@xxxxxxxxx>]

** Changed in: unity/7.2
       Status: In Progress => Fix Released

** Changed in: unity/7.2
    Milestone: 7.2.2 => 7.2.1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1307748

Title:
  xpathselect attribute matching doesn't match anything other than
  object Ids

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  I came across this issue while testing an autopilot branch of mine.

  The xpathselect server-side matching (as opposed to matching in the
  autopilot python code) is not working as expected.

  To reproduce:
    - Save this code as test_selection_attributes.py -  http://paste.ubuntu.com/7252495/ 
    - (with the unity-autopilot package installed) run: `autopilot run test_selection_attributes`

  This script contains 2 tests, one passes to prove that it can get a
  Launcher that has the monitor attribute of 0, the 2nd test attempts to
  select the Launcher object with attribute monitor=0 and fails.

  We see in the unity logs:
   -   "Unable to match 'monitor' against property of unknown integer type."

  A bit of digging suggests that GetPropertyValue is returning an array
  of values (Probably: Object type id, Value?) which means that, in
  MatchIntegerProperty for instance, the values GVariantClass will never
  be one of the Integer types.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1307748/+subscriptions