[Bug 22538] New: WebDAV: retry downloading item after interrupted transfer
by bugzilla@meego.com
https://bugs.meego.com/show_bug.cgi?id=22538
Summary: WebDAV: retry downloading item after interrupted
transfer
Classification: MeeGo Projects
Product: SyncEvolution
Platform: ---
Version: unspecified
Platform: Common
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: patrick.ohly(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
SyncEvolution 1.1.99.5.
When downloading data fails, the request should be retried. Instead
SyncEvolution fails with an XML parsing error. Example from
http://syncev.meego.com/2011-08-05-11-35_testing_dbus_apple_googlecalenda...
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLI]
[ERROR 00:00:06] call to empty boost::function
[ERROR 00:00:06] endCB DAV: response failed
[DEBUG 00:00:06] REPORT 'single item': Neon error code 1: Could not parse
response: Unknown error, must not retry
[DEVELOPER 00:00:06] stderr: Running destroy hooks.
It's unclear which boost::function is empty here. It must be one of those in
SyncEvolution's Neon CXX wrapper.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: Undecided
Keywords:
Status: NEW
Who: patrick.ohly(a)intel.com
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=22538
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
10 years, 1 month
[Bug 19432] New: CalDAV + Google: implement constant request rate
by bugzilla@meego.com
https://bugs.meego.com/show_bug.cgi?id=19432
Summary: CalDAV + Google: implement constant request rate
Classification: MeeGo Projects
Product: SyncEvolution
Platform: ---
Version: unspecified
Platform: Common
Architecture: ---
Status: NEW
Severity: enhancement
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: patrick.ohly(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
The Google calendar server starts sending 401 errors when too many requests are
sent. The current code detects that and then retries the same request after
increasing delays.
However, each new request is always sent immediately, and thus runs into the
same 401 error, and so on.
We should remember across requests that delays were necessary and thus sent
requests at a rate that the server considers acceptable, but not faster.
To reproduce the problem, try:
CLIENT_TEST_NUM_ITEMS=100 CLIENT_TEST_MODE=server CLIENT_TEST_SIMPLE_UID=1
CLIENT_TEST_UNIQUE_UID=1 CLIENT_TEST_SERVER=google-calendar
CLIENT_TEST_EVOLUTION_PREFIX=file:///tmp/test_ ./client-test
Client::Sync::eds_event::testManyItems
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: enhancement
Priority: Undecided
Keywords:
Status: NEW
Who: patrick.ohly(a)intel.com
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=19432
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
10 years, 1 month