[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.
12 years, 1 month
[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.
12 years, 1 month
[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.
12 years, 1 month
[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.
12 years, 1 month
[Bug 7210] New: stable D-Bus API
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=7210
Summary: stable D-Bus API
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: ASSIGNED
Severity: normal
Priority: P1
Component: *Feature Request
AssignedTo: syncevolution(a)lists.intel.com
ReportedBy: patrick.ohly(a)intel.com
CC: syncevolution(a)lists.intel.com
Depends on: 3602,3603,5042,5043,6370,6376,6548,7134
Release Milestone: Undecided
The goals of the redesigned D-Bus API are:
* well documented and designed
* stable
* usable by multiple frontends at the same time
* support connect/disconnect of frontends and syncing in the background
* support incoming connections, for example from obexd
This issue is a meta issue tracking various aspects of this task.
We have automated testing of some parts of the new D-Bus API, but as always,
probably not enough. Most of the API will be exercised by
a) the sync UI
b) incoming OBEX connections
so covering that should go a long way towards covering the D-Bus API.
--
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.
12 years, 1 month
[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.
12 years, 1 month
[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.
12 years, 1 month
[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.
12 years, 1 month
[Bug 8511] New: Compile for maemo 5
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=8511
Summary: Compile for maemo 5
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: MID
OS/Version: Other
Status: NEW
Severity: major
Priority: Undecided
Component: *Feature Request
AssignedTo: syncevolution(a)lists.intel.com
ReportedBy: mikhmv(a)gmail.com
CC: syncevolution(a)lists.intel.com
Hi,
Can anybody compile syncevolution for maemo 5?
I tried do it but fail...
I don't have enough experience...
--
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.
12 years, 1 month
[Bug 4815] New: Outlook meeting invitations: timezones
by bugzilla＠moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=4815
Summary: Outlook meeting invitations: timezones
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Generic
OS/Version: Other
Status: ASSIGNED
Severity: major
Priority: P1
Component: * Feature Request
AssignedTo: syncevolution(a)lists.intel.com
ReportedBy: patrick.ohly(a)intel.com
CC: syncevolution(a)lists.intel.com
This was originally found when syncing an Evolution calendar with a meeting
invitation created by Outlook with ScheduleWorld.
Outlook's VTIMEZONE definitions are nasty because the ID is not unique enough
to identify the location. Software that supports VTIMEZONE to evaluate the
times doesn't have a problem, as long as it handles different VTIMEZONE
definitions for the same ID correctly (Evolution had a bug around that).
Many servers, including ScheduleWorld and Funambol, have to map the VTIMEZONE
to some internal time zone database because they cannot use the original
definition, or because they need to send to a client which doesn't.
This mapping is fragile and unreliable if the ID doesn't follow the Olson
pseudo-standard and contains the location. In my case, "TZID:Pacific Standard
Time" was mapped to "America/Bogota", presumably because the GMT offsets kind
of matched. It then was displayed incorrectly.
A client shouldn't have to deal with these issues. But because we are now
working towards implementing a server, we need this kind of mapping code
ourselves and once we have it, might as well use it in our client. The goal is
that the client always uses Olson TZID strings when talking to a SyncML server.
That way we have that timezone matching code under our control and can tune
and/or fix it. Right now we depend on server developers to do it for us.
The Synthesis timezone handling code doesn't do that for us quite yet. It does
match based on Olson TZID if libical is found, so those TZIDs are covered. For
Outlook TZIDs it falls back to matching against an internal list, without using
Olson TZID strings for those if a match is found. We should change that so that
the list has TZID aliases with the Olson name and use those names when encoding
a VTIMEZONE. Not sure whether this change is acceptable upstream; need to
discuss and perhaps make it configurable.
If no match is found, then a temporary time zone definition is used, but it is
not preserved in the database unless the database stores VTIMEZONEs. In other
words, Evolution is fine, the ODBC backend is not. If we use the later in a
server, we need to fix this issue.
I can dig out the example, but we need more than one anyway. Ideally we need
examples for the whole range of Outlook and Exchange (they can be different!)
VTIMEZONE definitions, extend out test suite to cover the conversion, then work
on correctly identifying all these timezones.
--
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.
12 years, 1 month