[Bug 19433] New: CalDAV + Google: incorrect 404 for GET
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=19433
Summary: CalDAV + Google: incorrect 404 for GET
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
>From a testManyItems test:
[INFO @google 00:03:16] @google/calendar: adding "030-phone meeting, 030-my
office"
[DEBUG @google 00:03:16] starting PUT
[DEBUG @google 00:03:17] update item status: <status 1.1, code 201, class 2,
Created>
[DEBUG @google 00:03:17] starting PROPFIND
[DEBUG @google 00:03:17] item
UNIQUE-UID-1308257075-030-UNIQUE-UID-1308257075-1234567890(a)dummy.ics = rev
63443940431
[DEBUG @google 00:03:17] starting GET
[DEBUG @google 00:03:18] resending VEVENT to get rid of VALARM
[DEBUG @google 00:03:18] starting PUT
[DEBUG @google 00:03:19] update item status: <status 1.1, code 204, class 2, No
Content>
[DEBUG @google 00:03:19] starting PROPFIND
[DEBUG @google 00:03:19] PROPFIND: Neon error code 1: 404 Not Found, must not
retry
[DEBUG @google 00:03:19] @google/calendar: exception thrown at
/home/pohly/syncevolution/syncevolution/src/backends/webdav/NeonCXX.cpp:649
[ERROR @google 00:03:19] @google/calendar: error code from SyncEvolution object
not found (remote, status 404): PROPFIND: Neon error code 1: 404 Not Found
This is a temporary error, trying again (as in a --print-items command line
operation) shows the event:
UNIQUE-UID-1308257075-030-UNIQUE-UID-1308257075-1234567890%40dummy%2eics:
030-phone meeting, 030-my office
The retry mechanism should be triggered in those cases where we are pretty sure
that 404 must be incorrect.
--------
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=19433
--
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.
8 years, 5 months
[Bug 14891] New: [pretest] Mobical.net is changed to everdroid.com
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=14891
Summary: [pretest] Mobical.net is changed to everdroid.com
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: major
Priority: High
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: jingke.zhang(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
Created an attachment (id=5109)
--> (https://bugs.meego.com/attachment.cgi?id=5109)
everdroid service
BUILD IMAGE: BUILD IMAGE:: meego-netbook-ia32-1.1.90.8.20110323.1
HARDWARE MODEL (on what HW this bug is uncovered): netbook
BUG DETAILED DESCRIPTIONS
===========================================================
We failed to do two-way sync with mobical. Then, log on to its website, find
the www.mobical.net is automatically redirected to www.everdroid.com (please
see attachment).
Developer, please confirm that change. If so, we need to know: will we support
mobical in the future? High priority to get answer. Thanks!
--
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.
8 years, 5 months
[Bug 20990] New: auto sync: determine transport of local sync configs
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=20990
Summary: auto sync: determine transport of local sync configs
Classification: MeeGo Projects
Product: SyncEvolution
Platform: ---
Version: unspecified
Platform: Common
Architecture: ALL
Status: NEW
Severity: normal
Priority: High
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
Depends on: 20970
Blocks: 20966
Estimated Hours: 0.0
Auto-syncing of local sync configs probably doesn't work at the moment because
they never match the "peer is online" checks in the AutoSyncManager code.
The manager should determine what the peer needs based on peerType. Checking
the target config's syncURL doesn't work well because there might not be any.
There also needs to be fallback for "don't know whether it works", in which
case syncing should be allowed.
--- Comment #1 from pohly <patrick.ohly(a)intel.com> 2011-07-12 14:32:19 UTC ---
+++ This bug was initially created as a clone of Bug #20970 +++
The manager should determine what the peer needs based on peerType. Checking
the target config's syncURL doesn't work well because there might not be any.
Right now the code assumes that local:// sync depends on HTTP:
} else if (boost::istarts_with(url, "local")) {
// TODO: instead of assuming that local sync needs HTTP, really
look into the target config
// and determine what the peerType is
transport = AutoSyncTask::NEEDS_HTTP;
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: High
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=20990
--
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.
8 years, 5 months
[Bug 20967] New: auto sync: correctly invoke GTK UI
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=20967
Summary: auto sync: correctly invoke GTK UI
Classification: MeeGo Projects
Product: SyncEvolution
Platform: ---
Version: unspecified
Platform: Common
Architecture: ---
Status: NEW
Severity: major
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
Salvatore's refactoring of the notifcation mechanism removed the passing of the
right command line arguments to the GTK sync-ui. See
//TODO: set config information for 'sync-ui'
in syncevo-dbus-server.cpp.
Must re-enable that before releasing 1.1.99.5, otherwise we have a regression.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: major
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=20967
--
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.
8 years, 5 months
[Bug 19488] New: local configurations should always be 'present'
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=19488
Summary: local configurations should always be 'present'
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: jku(a)linux.intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
Local configs currently always have "No transport" presence. The right (or at
least better) value would be to always return "" (as in MIGHTWORK).
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: Undecided
Keywords:
Status: NEW
Who: jku(a)linux.intel.com
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=19488
--
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.
8 years, 5 months
[Bug 19484] New: CalDAV + Google: meeting invitations
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=19484
Summary: CalDAV + Google: meeting invitations
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
The Google server seems to think that it can take over meeting
acceptance/decline handling when new events are stored on the server.
For example, PARTSTAT=ACCEPTED gets replaced with PARTSTAT=NEEDS-ACTION.
It has also been observed that participants and organizer get overwritten.
There might be nothing that we can do about it. Investigating a bit more would
be worthwhile, though.
In the meantime I'm simplifying the test/testcases/google_event.ics by removing
the "meeting invitiation" test case.
--------
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=19484
--
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.
8 years, 5 months
[Bug 16693] New: The "Direct sync" function fails(Bluetooth)
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=16693
Summary: The "Direct sync" function fails(Bluetooth)
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: rextsai(a)linpus.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
BUILD IMAGE(X.X.XX.X.XXXXXXXX.X - (e.g.:
meego-netbook-ia32-1.0.90.0.20100831.1)):
HARDWARE MODEL (on what HW this bug is uncovered):
BUG DETAILED DESCRIPTIONS
===========================================================
The "Direct sync" function fails(Bluetooth).
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
===========================================================
1.In Bluetooth panel, search bluetooth devices and pair successful
2.Launch "Sync" application
3.Press "Select sync service" button
4.In Direct sync, no show any devices.
5.
EXPECTED OUTCOME:
===================
In Direct sync, show devices.
ACTUAL OUTCOME:
===================
In Direct sync, no show any devices.
USER IMPACT:
===================
REPRODUCIBILITY:
(always, less than 1/10, 5/10, 9/10)
=====================================
EXTRA SOFTWARE INSTALLED:
============================
OTHER COMMENTS:
===================
--
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.
8 years, 8 months
[Bug 14804] New: hard-coded rule and code for "supports UID"
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=14804
Summary: hard-coded rule and code for "supports UID"
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: High
Component: SyncEvolution
AssignedTo: patrick.ohly(a)intel.com
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
Currently the local sync code assumes that both sides have a real, persistent,
creator-assigned UID (as in iCalendar 2.0).
This is not the case for all peers, even those using iCalendar 2.0.
It would be nice if we could use some CtCap extensions which says "yes, I
really support real UIDs" in contrast to just saying "I have a UID property".
Depends on changes in libsynthesis and SyncEvolution.
The code also uses a rather ugly pre-processing step of the config:
commit 391e1fd5554fd09597ca3eb626a308db497ec61a
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Tue Nov 16 12:21:08 2010 +0100
local sync: rely on iCalendar 2.0 UID/RECURRENCE-ID for pairing
This patch should be reverted and be replaced by a merge script which compares
the UIDs if (and only if) possible. This is a nicer solution (less code) and
can decide about UID usage after receiving the CtCap (in contrast to the
pre-processing step).
I'd like to get at least the second part into 1.2.
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
8 years, 8 months
[Bug 22783] New: add<->add conflicts: detect match based on UID, merge data
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=22783
Summary: add<->add conflicts: detect match based on UID, merge
data
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
Currently <Add> requests for already existing calendar items are detected by
the SyncEvolution backends. This has several drawbacks:
1. engine ID tracking may get confused
2. data does not get merged (backends don't have code for it)
See "[SyncEvolution] UID matching during add<->add conflict".
Lukas has a solution for point 1 and suggested an approach for point 2.
--------
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=22783
--
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.
8 years, 8 months
[Bug 21541] New: D-Bus server:
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=21541
Summary: D-Bus server:
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
>From nightly testing, shortly after 1.1.99.5:
TestDBusServerPresence.testPresenceSignal - check Server.Presence signal ...
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in
maybe_handle_message
self._handler(*args, **kwargs)
File "/work/runtests/head/syncevolution/test/test-dbus.py", line 973, in
cb_bt_presence
"obex-bt://temp-bluetooth-peer-changed-from-http")
File "/usr/lib/python2.6/unittest.py", line 350, in failUnlessEqual
(msg or '%r != %r' % (first, second))
AssertionError: dbus.UTF8String('http://http-only-1') !=
'obex-bt://temp-bluetooth-peer-changed-from-http'
ok
The test needs to be fixed, it shouldn't test assertions inside the callback
because the D-Bus layer swallows these exceptions. Found after adding "-u" to
the python invocation (disabled buffering of stdout).
--------
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=21541
--
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.
9 years