[Bug 6456] New: syncevolution --version: information about backends?
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=6456
Summary: syncevolution --version: information about backends?
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: ASSIGNED
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: congwu.chen(a)intel.com
ReportedBy: patrick.ohly(a)intel.com
QAContact: yanshuang.zheng(a)intel.com
CC: shuang.wan(a)intel.com, syncevolution(a)lists.intel.com
Release Milestone: Undecided
What information do we want to display to users about backends?
In 0.9, "syncevolution --version" didn't print anything about them.
In the current "master", it prints:
Scanning backend libraries in backends/
Scanning backend libraries in backends/addressbook/.libs/
Scanning backend libraries in backends/file/.libs/
Scanning backend libraries in backends/evolution/.libs/
Scanning backend libraries in backends/sqlite/.libs/
I think for end users it would be more useful to print the backends which were
really loaded. Congwu, can you change this for 0.9.1?
Note that I fixed a memory handling problem in SyncSourceBackendsInfo/Debug()
and turned the functions into static methods of SyncSource, like the related
createSource() method.
I don't think we have a version number for backends. If we had, this should
also go into this output. In 1.0 perhaps?
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
10 years, 7 months
[Bug 6303] New: extend vCard field list (Memotoo)
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=6303
Summary: extend vCard field list (Memotoo)
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: ASSIGNED
Severity: normal
Priority: P2
Component: * Feature Request
AssignedTo: syncevolution(a)lists.intel.com
ReportedBy: patrick.ohly(a)intel.com
CC: syncevolution(a)lists.intel.com
Release Milestone: Undecided
Please include a detailed description as well as steps to reproduce the bug.
The following vCard properties are in use by Memotoo:
X-SKYPE-USERNAME:skype id
X-EVOLUTION-ASSISTANT-TEL:assistant's phone
X-EVOLUTION-PARENT:parents
X-EVOLUTION-CHILDREN:children
X-SYNCEVOLUTION-FBURL:http://www.memotoo.com/contactsIFB.php?uid=73fc9832...
None of them are currently detected by the Synthesis config.
We need to do three things:
1. figure out how we can have properties in the main configuration
which are not supported by the active backend
2. add X-SKYPE-USERNAME, X-EVOLUTION-PARENT, X-EVOLUTION-CHILDREN,
X-EVOLUTION-ASSISTANT-TEL; see bug #3473
3. map between X-SYNCEVOLUTION-FBURL and FBURL, see X-[EVOLUTION-]SPOUSE
Adding the new properties without solving 1 has the undesirable effect that the
SyncML server gets wrong information about the client, because the DevInf would
include properties not supported by the data source.
--
Configure bugmail: http://bugzilla.moblin.org/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, 7 months
[Bug 6378] New: automatic sync
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=6378
Summary: automatic sync
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: NEW
Severity: normal
Priority: P2
Component: * Feature Request
AssignedTo: syncevolution(a)lists.intel.com
ReportedBy: patrick.ohly(a)intel.com
CC: syncevolution(a)lists.intel.com
Release Milestone: Undecided
We want some form of automatic syncs in SyncEvolution 1.0. Probably something
based on polling will be good enough initially. This issue is just a reminder
that we need to discuss this in more detail. Eventually it'll depend on more
specific sub-problems, covering:
* starting a daemon to control the automatism
* detect errors which require user intervention
* notifications
--
Configure bugmail: http://bugzilla.moblin.org/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, 7 months
[Bug 6457] New: nightly testing + valgrind results
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=6457
Summary: nightly testing + valgrind results
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: ASSIGNED
Severity: normal
Priority: P1
Component: SyncEvolution
AssignedTo: yongsheng.zhu(a)intel.com
ReportedBy: patrick.ohly(a)intel.com
QAContact: yanshuang.zheng(a)intel.com
CC: shuang.wan(a)intel.com, syncevolution(a)lists.intel.com
Release Milestone: Undecided
While running some routine valgrind checks of the dbus-api branch I noticed a
regression imported from "master" (invalid memory access to result of
SyncSourceBackendDebug()). The code went into "master" earlier last week. The
nightly testing should have found this problem, because syncs should be run
under valgrind control.
Do we still do that? If we do, did valgrind find the problem? It should be
reported at the end of the client-test run to stdout/stderr and result in a
non-zero return code of client-test.
I suspect that since the migration to the HTML format for test results this
particular aspect of testing is no longer included in the output and thus might
have been missed last week.
Yongsheng, can you check this?
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
10 years, 7 months
[Bug 5631] New: Egroupware
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=5631
Summary: Egroupware
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncML
AssignedTo: patrick.ohly(a)intel.com
ReportedBy: Dries.Decock(a)telenet.be
QAContact: yanshuang.zheng(a)intel.com
CC: shuang.wan(a)intel.com, syncevolution(a)lists.intel.com
Release Milestone: Undecided
In syncevolution <0.9, syncing with egroupware worked. Now, I got the following
error :
# [2009-08-25 16:32:56.313] ===> smlProcessData failed, returned 0x2012
#
+
–
[2009-08-25 16:32:56.313] 'SessionAbort' - Aborting Session, Status=20007,
ProblemSource=LOCAL [--][++] [->end]
* [2009-08-25 16:32:56.313] WARNING: Aborting Session with Reason Status
20007 (LOCAL problem) ***
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
10 years, 7 months
[Bug 4774] New: verify a server's conflict handling policy
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=4774
Summary: verify a server's conflict handling policy
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Generic
OS/Version: Other
Status: ASSIGNED
Severity: normal
Priority: P3
Component: * Feature Request
AssignedTo: syncevolution(a)lists.intel.com
ReportedBy: patrick.ohly(a)intel.com
CC: guannan.ou(a)intel.com, syncevolution(a)lists.intel.com
Depends on: 4369
As described in bug #4369, conflict handling can vary considerably between
servers. It would be useful to include tests in client-test which simulate the
various conflicts and identify how the server resolves them.
Then for known servers, we could also check whether the current result a) is
sane and b) is the one wanted by the server developers. This may be overkill
for all of the servers we test with, but for our own we would definitely need
this.
+++ This bug was initially created as a clone of Bug #4369 +++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
When I tried the following test with scheduleworld, I see that the policy is
“client-win”, contact information is deleted on server. But with funambol, the
updated contact A is synced to client. Can you please check which policy should
we follow?
====================================================
Test Step:
1. add contact A on client, try two-way sync with server.
2. delete contact A on client, and update contact A on server.
3. try two-way sync.
====================================================
--
Configure bugmail: http://bugzilla.moblin.org/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, 7 months
[Bug 4631] New: Google: ORG data is not consistent after two-way/slow sync between seperately updated client and server
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=4631
Summary: Google: ORG data is not consistent after two-way/slow
sync between seperately updated client and server
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: patrick.ohly(a)intel.com
ReportedBy: guannan.ou(a)intel.com
QAContact: yanshuang.zheng(a)intel.com
CC: shuang.wan(a)intel.com, syncevolution(a)lists.intel.com,
congwu.chen(a)intel.com
---------------------------------
Summary
---------------------------------
ORG data is not consistent after two-way/slow sync between seperately updated
client and server.
---------------------------------
Reproduce Step
---------------------------------
<1> add one contact name: Jessy, Company “Intel”
<2> two-way sync
<3> modify local contact’s Company as “Intel(PRC)”
<4> modify google server contact’s Company as “Intel(US)”
<5> two-way sync again.
Company filed of contact “Jessy” is not consistent in client and server.
Result shows that in client, Company is still "Intel(PRC)", in server, Company
is still "Intel(US)".
Test the same step in Funambol, client updated contact information will replace
the corresponding server's contact.
------------------------
last sync outgoing data
------------------------
BEGIN:VCARD
VERSION:2.1
REV:20090722T142205Z
N:;Monday;;;
FN:Monday
X-EVOLUTION-FILE-AS:Monday
NICKNAME:
TITLE:
ORG:intelClient11;;;
ROLE:
TEL;CELL:33333333
TEL:111111111111111111111111111111
TEL;CELL:22222222
EMAIL:
URL:
X-MOZILLA-HTML:
ADR:;;;;;;
BDAY:
NOTE:
PHOTO:
END:VCARD
-------------------------
last sync incoming data
-------------------------
BEGIN:VCARD
VERSION:2.1
FN:Monday
N:;Monday;;;
TEL;CELL:33333333
TEL:111111111111111111111111111111
TEL;CELL:22222222
ORG:intelServer
ORG:intelClient11
TITLE:
NOTE:
ADR:;;;;;;
X-EVOLUTION-FILE-AS:Monday
NICKNAME:
ROLE:
URL:
X-MOZILLA-HTML:
BDAY:
END:VCARD
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
10 years, 7 months
[Bug 5041] New: avoid use of stdout/cout, route through our own logging code
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=5041
Summary: avoid use of stdout/cout, route through our own
logging code
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Generic
OS/Version: Other
Status: ASSIGNED
Severity: normal
Priority: P2
Component: * Feature Request
AssignedTo: syncevolution(a)lists.intel.com
ReportedBy: patrick.ohly(a)intel.com
CC: syncevolution(a)lists.intel.com
Usage of stdout and cout should be avoided. Currently the SyncEvolutionCmdline
class is still told to write into cout by syncevolution.cpp.
When compiling SyncEvolution .cpp code, any reference to stdout or cout should
trigger a compiler error (redefine the symbols?!). Some with printf, puts, etc.
Instead of cout, a custom stream which passes the data into our logging system
with a suitable tag that reproduces the output verbatim on the console and logs
it in the normal log should be used.
Running commands must redirect stdout of the processes and ideally keep
processing that output while the command runs (rules out simple system()
calls).
--
Configure bugmail: http://bugzilla.moblin.org/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, 7 months
[Bug 5042] New: D-Bus API: send log output to clients
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=5042
Summary: D-Bus API: send log output to clients
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Generic
OS/Version: Other
Status: ASSIGNED
Severity: major
Priority: P2
Component: * Feature Request
AssignedTo: syncevolution(a)lists.intel.com
ReportedBy: patrick.ohly(a)intel.com
CC: syncevolution(a)lists.intel.com
Depends on: 5041
Running the D-Bus server in a console is a useful debugging trick to see
problem reports that are not visible in the GUI. It should be possible to get
much of the same effect by adding a signal to the D-Bus API which broadcasts
the console part of the log to clients.
Clients then can either print it on their own console or present it in an
"advanced progress" area, much like APT GUIs show the output of aptitude.
However, in contrast to aptitude, the SyncEvolution logging is not meant to be
translated.
--
Configure bugmail: http://bugzilla.moblin.org/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, 7 months
[Bug 5043] New: move command line into D-Bus server
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=5043
Summary: move command line into D-Bus server
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Generic
OS/Version: Other
Status: ASSIGNED
Severity: normal
Priority: P2
Component: * Feature Request
AssignedTo: syncevolution(a)lists.intel.com
ReportedBy: patrick.ohly(a)intel.com
CC: syncevolution(a)lists.intel.com
Depends on: 5041,5042
With output redirection working (#5041) and logging sent to clients (#5042) it
should be fairly easy to just pass all of argv to a new D-Bus method and have
it processed as part of the syncevo-dbus-server. In that mode, syncevolution is
really just another client of the single instance which controls syncs.
Care has to be taken to properly serialize requests by syncevolution with
on-going operations.
A new command line option "--monitor" would be useful to connect to a running
sync session. "--status" without server config parameter could be used to query
whether there is any sync running.
--
Configure bugmail: http://bugzilla.moblin.org/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, 7 months