Attachment 86386 Details for Bug 49389 – 07/16] Fix more uses of RequestHandles

[patch] 07/16] Fix more uses of RequestHandles

0007-Fix-more-uses-of-RequestHandles.patch (text/plain), 1.36 KB, created by Simon McVittie on 2013-09-23 15:14:25 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2013-09-23 15:14:25 UTC

Size: 1.36 KB

patch

obsolete

>From fd84264f548bbeadc04931f14d6bc2cd16e4584b Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Mon, 23 Sep 2013 13:59:53 +0100
>Subject: [PATCH 07/16] Fix more uses of RequestHandles
>
>---
> tests/twisted/roster/subscribe.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/tests/twisted/roster/subscribe.py b/tests/twisted/roster/subscribe.py
>index 102ab71..b1b9aa5 100644
>--- a/tests/twisted/roster/subscribe.py
>+++ b/tests/twisted/roster/subscribe.py
>@@ -33,7 +33,7 @@ def test(q, bus, conn, stream):
>     assertLength(0, subscribe.Group.GetMembers())
> 
>     # request subscription
>-    handle = conn.RequestHandles(cs.HT_CONTACT, ['suggs@night.boat.cairo'])[0]
>+    handle = conn.get_contact_handle_sync('suggs@night.boat.cairo')
>     call_async(q, subscribe.Group, 'AddMembers', [handle], '')
> 
>     # libpurple puts him on our blist as soon as we've asked; there doesn't
>@@ -75,7 +75,7 @@ def test(q, bus, conn, stream):
> 
>     # put a contact into the *group* explicitly: this shouldn't ask for
>     # subscription, but it does
>-    handle = conn.RequestHandles(cs.HT_CONTACT, ['ayria@revenge.world'])[0]
>+    handle = conn.get_contact_handle_sync('ayria@revenge.world')
>     call_async(q, def_group.Group, 'AddMembers', [handle], '')
> 
>     # libpurple puts her on our blist as soon as we've asked; there doesn't
>-- 
>1.8.4.rc3
>

Actions: View | Splinter Review

Attachments on bug 49389: 86380 | 86381 | 86382 | 86383 | 86384 | 86385 | 86386 | 86387 | 86388 | 86389 | 86390 | 86391 | 86392 | 86393 | 86394 | 86395

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.