sending payload from engine to client does not work

Bug #692645 reported by Seif Lotfy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Framework
Fix Released
High
Seif Lotfy

Bug Description

I wrote a test case in the below diff where I insert an event with a payload and try to retrieve it again. This does not work on trunk guys -.-
---

=== modified file 'test/remote-test.py'
--- test/remote-test.py 2010-09-22 18:44:16 +0000
+++ test/remote-test.py 2010-12-20 15:42:22 +0000
@@ -321,6 +321,19 @@
   registry = iface.get_extension("DataSourceRegistry", "data_source_registry")
   registry.GetDataSources()

+ def testFindEventsWithPayload(self):
+ mainloop = gobject.MainLoop()
+ payload = "Hello World"
+ def callback(ids):
+ def callback2(events):
+ mainloop.quit()
+ self.assertEquals(events[0].payload, payload)
+ self.client.get_events(ids, callback2)
+ events = [Event.new_for_values(actor=u"boo", timestamp=124, subject_uri="file://yomomma")]
+ events[0].payload = payload
+ self.client.insert_events(events, callback)
+ mainloop.run()
+
 class ZeitgeistRemoteInterfaceTest(unittest.TestCase):

  def setUp(self):

----

Run "./test/remote-test.py ZeitgeistRemoteAPITest.testFindEventsWithPayload"

I get:

Error from Zeitgeist engine: org.freedesktop.DBus.Python.TypeError: Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/service.py", line 745, in _message_cb
    _method_reply_return(connection, message, method_name, signature, *retval)
  File "/usr/lib/pymodules/python2.6/dbus/service.py", line 252, in _method_reply_return
    reply.append(signature=signature, *retval)
TypeError: an integer is required

Related branches

Seif Lotfy (seif)
description: updated
Changed in zeitgeist:
milestone: none → 0.7.0
status: New → In Progress
assignee: nobody → Seif Lotfy (seif)
Seif Lotfy (seif)
Changed in zeitgeist:
status: In Progress → Fix Committed
importance: Undecided → High
Seif Lotfy (seif)
Changed in zeitgeist:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.