Bug 537160 – Error Google Calendar Traceback

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 537160 - Error Google Calendar Traceback


Summary:	Error Google Calendar Traceback


Status:	RESOLVED DUPLICATE of bug 544708

Product:	conduit
Classification:	Other
Component:	dataproviders
Version:	0.3.x
Hardware:	Other All

Importance:	Normal normal
Target Milestone:	---
Assigned To:	conduit-maint@gnome.bugs
QA Contact:	conduit-maint@gnome.bugs

URL:
Whiteboard:

Depends on:
Blocks:	546088

Reported:	2008-06-07 20:08 UTC by Roumano
Modified:	2009-02-16 01:56 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Roumano 2008-06-07 20:08:56 UTC

Please describe the problem:
[Syncronization      ][DEBUG  ] Source Status = Ready (Synchronization.py:673)
** (conduit.real:11082): DEBUG: Opening calendar source uri: file:///home/roumano/.evolution/calendar/local/system

[Syncronization      ][CRITICAL] UNKNOWN REFRESH ERROR: Wrapper: Google Calendar twoway (UID: GoogleCalendarTwoWay-roumano@gmail.com)
Traceback (most recent call last):

+ Trace 199811

File "/home/roumano/conduit/1513/conduit/Synchronization.py", line 694 in run
```
sink.module.refresh()
```
File "/home/roumano/conduit/1513/conduit/modules/GoogleModule/GoogleModule.py", line 461 in refresh
```
for event in self._get_all_events():
```
File "/home/roumano/conduit/1513/conduit/modules/GoogleModule/GoogleModule.py", line 385 in _get_all_events
```
eventFeed = self.service.CalendarQuery(calQuery)
```
File "/home/roumano/conduit/1513/conduit/modules/GoogleModule/gdata/calendar/service.py", line 116 in CalendarQuery
```
converter=gdata.calendar.CalendarEventFeedFromString)
```
File "/home/roumano/conduit/1513/conduit/modules/GoogleModule/gdata/calendar/service.py", line 108 in Query
```
result = self.Get(uri, converter=converter)
```
File "/home/roumano/conduit/1513/conduit/modules/GoogleModule/gdata/service.py", line 551 in Get
```
'reason': server_response.reason, 'body': result_body}
```

RequestError: {'status': 400, 'body': 'Invalid UserId l49phas5g0sl5tb306tgjal70c%40group.calendar.google.com', 'reason': 'Bad Request'}

 (Synchronization.py:701)
[Syncronization      ][INFO   ] Not enough sinks refreshed (Synchronization.py:715)


Steps to reproduce:
1. Make a synchro form evolution calendar to google calendar
2. COnfigure the idem "google calendar", load calendar
3. Make a refresh on google calendar OR make the synchro ( same error )


Actual results:
Traceback

Expected results:


Does this happen every time?
yes

Other information:

Comment 1 Adam York 2008-08-01 17:06:08 UTC

I have the same bug.

I'm posting my output as well.

[Syncronization      ][INFO   ] Setting global cancel flag (Synchronization.py:90)
[Syncronization      ][DEBUG  ] Starting worker: <SyncWorker(Wrapper: Google Calendar twoway (UID: GoogleCalendarTwoWay-aaylnx) |--> [<conduit.ModuleWrapper.ModuleWrapper instance at 0x87c4c8c>], initial)> (Synchronization.py:93)
[Syncronization      ][DEBUG  ] Sync <SyncWorker(Wrapper: Google Calendar twoway (UID: GoogleCalendarTwoWay-aaylnx) |--> [<conduit.ModuleWrapper.ModuleWrapper instance at 0x87c4c8c>], started)> beginning. Slow: False, Twoway: False (Synchronization.py:627)
[Syncronization      ][DEBUG  ] Syncworker state 0 (Synchronization.py:646)
[Syncronization      ][DEBUG  ] Syncworker state 1 (Synchronization.py:646)
[Syncronization      ][DEBUG  ] Source Status = Ready (Synchronization.py:675)
[Syncronization      ][CRITICAL] UNKNOWN REFRESH ERROR: Wrapper: Google Calendar twoway (UID: GoogleCalendarTwoWay-aaylnx)
Traceback (most recent call last):

+ Trace 204376

File "/var/lib/python-support/python2.5/conduit/Synchronization.py", line 678 in run
```
self.source.module.refresh()
```
File "/usr/lib/conduit/modules/GoogleModule/GoogleModule.py", line 462 in refresh
```
for event in self._get_all_events():
```
File "/usr/lib/conduit/modules/GoogleModule/GoogleModule.py", line 386 in _get_all_events
```
eventFeed = self.service.CalendarQuery(calQuery)
```
File "/usr/lib/conduit/modules/GoogleModule/gdata/calendar/service.py", line 116 in CalendarQuery
```
converter=gdata.calendar.CalendarEventFeedFromString)
```
File "/usr/lib/conduit/modules/GoogleModule/gdata/calendar/service.py", line 108 in Query
```
result = self.Get(uri, converter=converter)
```
File "/usr/lib/conduit/modules/GoogleModule/gdata/service.py", line 551 in Get
```
'reason': server_response.reason, 'body': result_body}
```

RequestError: {'status': 400, 'body': 'Invalid UserId 4nk73ltml6f9ddg6qo0eqhhr3o%40group.calendar.google.com', 'reason': 'Bad Request'}

 (Synchronization.py:686)
[Syncronization      ][WARNING] Sync Aborted (Synchronization.py:778)
[Syncronization      ][DEBUG  ] Deleting worker: <SyncWorker(Wrapper: Google Calendar twoway (UID: GoogleCalendarTwoWay-aaylnx) |--> [<conduit.ModuleWrapper.ModuleWrapper instance at 0x87c4c8c>], stopped)> (Synchronization.py:86)

Any feedback on this bug?  It pretty much renders google calendar syncing useless.

Comment 2 Adam York 2008-08-01 17:08:54 UTC

(In reply to comment #1)
> I have the same bug.
> 
> I'm posting my output as well.
> 
> [Syncronization      ][INFO   ] Setting global cancel flag
> (Synchronization.py:90)
> [Syncronization      ][DEBUG  ] Starting worker: <SyncWorker(Wrapper: Google
> Calendar twoway (UID: GoogleCalendarTwoWay-aaylnx) |-->
> [<conduit.ModuleWrapper.ModuleWrapper instance at 0x87c4c8c>], initial)>
> (Synchronization.py:93)
> [Syncronization      ][DEBUG  ] Sync <SyncWorker(Wrapper: Google Calendar
> twoway (UID: GoogleCalendarTwoWay-aaylnx) |-->
> [<conduit.ModuleWrapper.ModuleWrapper instance at 0x87c4c8c>], started)>
> beginning. Slow: False, Twoway: False (Synchronization.py:627)
> [Syncronization      ][DEBUG  ] Syncworker state 0 (Synchronization.py:646)
> [Syncronization      ][DEBUG  ] Syncworker state 1 (Synchronization.py:646)
> [Syncronization      ][DEBUG  ] Source Status = Ready (Synchronization.py:675)
> [Syncronization      ][CRITICAL] UNKNOWN REFRESH ERROR: Wrapper: Google
> Calendar twoway (UID: GoogleCalendarTwoWay-aaylnx)
> Traceback (most recent call last):
>   File "/var/lib/python-support/python2.5/conduit/Synchronization.py", line
> 678, in run
>     self.source.module.refresh()
>   File "/usr/lib/conduit/modules/GoogleModule/GoogleModule.py", line 462, in
> refresh
>     for event in self._get_all_events():
>   File "/usr/lib/conduit/modules/GoogleModule/GoogleModule.py", line 386, in
> _get_all_events
>     eventFeed = self.service.CalendarQuery(calQuery)
>   File "/usr/lib/conduit/modules/GoogleModule/gdata/calendar/service.py", line
> 116, in CalendarQuery
>     converter=gdata.calendar.CalendarEventFeedFromString)
>   File "/usr/lib/conduit/modules/GoogleModule/gdata/calendar/service.py", line
> 108, in Query
>     result = self.Get(uri, converter=converter)
>   File "/usr/lib/conduit/modules/GoogleModule/gdata/service.py", line 551, in
> Get
>     'reason': server_response.reason, 'body': result_body}
> RequestError: {'status': 400, 'body': 'Invalid UserId
> 4nk73ltml6f9ddg6qo0eqhhr3o%40group.calendar.google.com', 'reason': 'Bad
> Request'}
>  (Synchronization.py:686)
> [Syncronization      ][WARNING] Sync Aborted (Synchronization.py:778)
> [Syncronization      ][DEBUG  ] Deleting worker: <SyncWorker(Wrapper: Google
> Calendar twoway (UID: GoogleCalendarTwoWay-aaylnx) |-->
> [<conduit.ModuleWrapper.ModuleWrapper instance at 0x87c4c8c>], stopped)>
> (Synchronization.py:86)
> 
> Any feedback on this bug?  It pretty much renders google calendar syncing
> useless.
> 

BTW, I forgot to say that I'm running 0.3.12 on ubuntu if that helps.

Comment 3 Antoine Cailliau 2008-10-05 14:04:14 UTC

There is already the same bug submitted : #544708

Comment 4 John Stowers 2009-02-16 01:56:59 UTC


*** This bug has been marked as a duplicate of 544708 ***