October 2012 - Syncevolution-issues

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=55918 Priority: high Bug ID: 55918 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Blocks: 55916 Summary: PIM API performance Severity: enhancement Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: NEW Version: unspecified Component: SyncEvolution Product: SyncEvolution Performance and resource consumption of the PIM API implementation is relevant in several ways: - writing to disk must be minimized (because of flash write cycle limitations) - response times for queries, in particular caller ID lookups, must be small enough to not be noticable by a human user; the goal is < 30ms for high numbers of contacts (10000). Compared to other embedded devices like phones or tablets, an IVI head unit typically has a faster CPU and more RAM (4GB?!). The implementation tries to achieve these goals by not building up complex data structures on disk for on-disk searching. Instead it assembles the unified address book in memory and searches there. If necessary, additional shortcuts might be implemented: - pre-start daemon to load contacts into memory during head unit startup - do on-disk search for caller ID while still assembling the in-memory data structure Before doing that, performance measurements will be needed. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 years, 11 months

1
20
0 / 0

[Bug 55926] New: PIM API: folks improvements

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=55926 Priority: medium Bug ID: 55926 CC: syncevolution-issues(a)syncevolution.org Assignee: patrick.ohly(a)gmx.de Blocks: 55918 Summary: PIM API: folks improvements Severity: enhancement Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: unspecified Component: SyncEvolution Product: SyncEvolution The unified address book is implemented by libfolks and the libfolks-eds backend: https://live.gnome.org/Folks This meta-issue tracks open issues in folks. -- You are receiving this mail because: You are on the CC list for the bug.

3 years, 11 months

1
12
0 / 0

[Bug 56141] New: PIM API wish list

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=56141 Priority: medium Bug ID: 56141 CC: syncevolution-issues(a)syncevolution.org Assignee: patrick.ohly(a)intel.com Summary: PIM API wish list Severity: enhancement Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: unspecified Component: SyncEvolution Depends on: 55916 Product: SyncEvolution A meta issue tracking issues which are not essential for the PIM API (issue #55916). -- You are receiving this mail because: You are on the CC list for the bug.

3 years, 11 months

1
31
0 / 0

[Bug 55916] New: D-Bus PIM API

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=55916 Priority: highest Bug ID: 55916 CC: syncevolution-issues(a)syncevolution.org Assignee: patrick.ohly(a)intel.com Summary: D-Bus PIM API Severity: normal Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: unspecified Component: SyncEvolution Product: SyncEvolution The API implements in-vehicle infotainment (IVI) use cases around contacts: - cache address books from peers (primarily phones connected via Bluetooth) in local address books - provide a unified address book that combines a configurable (and changing) subset of the local address books - fast phone number lookup - browsing and searching in the unified address book Tasks that are expected to be done by the user of this API: - identify peers and their capabilities - decide how and when peer data should be cached - define which data goes into the unified address book In other words, the API provides the mechanisms and the user the policy. This is a meta-issue that tracks the initial definition and development of that API in SyncEvolution. The corresponding public discussion is here (please use gmane's "reply" feature to join the mail thread): http://comments.gmane.org/gmane.comp.mobile.syncevolution/4009 The source is in the "pim" branch of http://cgit.freedesktop.org/SyncEvolution/syncevolution -- You are receiving this mail because: You are on the CC list for the bug.

3 years, 11 months

1
30
0 / 0

[Bug 54998] New: disable PHOTO syncing for specific peers

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=54998 Bug #: 54998 Summary: disable PHOTO syncing for specific peers Classification: Unclassified Product: SyncEvolution Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: high Component: SyncML AssignedTo: syncevolution-issues(a)syncevolution.org ReportedBy: patrick.ohly(a)gmx.de CC: syncevolution-issues(a)syncevolution.org Some peers, in particular older phones, have problems when being sent lots of photo data. It may be more useful to exclude photo data altogether for such peers. See "[SyncEvolution] Sync failure due to large addressbook entires." A possible solution would be: - introduce a new session variable in the <sessioninitscript> - set that variable in remote rules (see stripUID for an example) or based on a new config property (see preventSlowSync) - extend the <outgoingscript> for contacts such that it unsets the PHOTO property before encoding a contact for the peer if that session variable is set - see VCARD_OUTGOING_PHOTO_INLINING_SCRIPT That should take care of sending data to the phone. Ensuring that the photo doesn't get lost when receiving an update is harder. Something might be possible with a custom <mergescript>, but I am not sure whether it really gets invoked during a normal import. Alternatively, dynamically updating the field attributes after parsing the peer's CtCap would be a more elegant solution, because it would use existing libsynthesis mechanisms: - don't send properties to a peer which the peer doesn't support (strip PHOTO when sending) - preserve local properties not supported by the peer (preserve PHOTO) However, implementing that will require considerable changes in libsynthesis: - expose the field list attributes to scripts - ensure that a script is called after parsing CtCap and before using the field list (perhaps <datastoreinitscript> is suitable) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.

3 years, 11 months

1
2
0 / 0

[Bug 55921] New: no logging during local sync

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=55921 Priority: high Bug ID: 55921 CC: syncevolution-issues(a)syncevolution.org Assignee: patrick.ohly(a)gmx.de Blocks: 55918 Summary: no logging during local sync Severity: enhancement Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: unspecified Component: SyncEvolution Product: SyncEvolution The local sync in the IVI use case must not write anything to disk except for the actual data changes. This means: - disable logging in .cache/syncevolution - don't write sync meta data to .config/syncevolution for PBAP, because it always does a slow sync and needs no meta data. -- You are receiving this mail because: You are on the CC list for the bug.

8 years, 2 months

1
4
0 / 0

[Bug 54906] New: support IPv6 on syncevolution.org

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=54906 Bug #: 54906 Summary: support IPv6 on syncevolution.org Classification: Unclassified Product: SyncEvolution Version: unspecified Platform: Other URL: https://bugs.meego.com/show_bug.cgi?id=25562 OS/Version: All Status: ASSIGNED Severity: enhancement Priority: low Component: SyncEvolution AssignedTo: syncevolution-issues(a)syncevolution.org ReportedBy: patrick.ohly(a)gmx.de CC: syncevolution-issues(a)syncevolution.org As pointed out in https://bugs.meego.com/show_bug.cgi?id=25562 the initial IPv6 setup on syncevolution.org did not work (some kind of SSL certificate issue when used over IPv6). Therefore the IPv6 address of syncevolution.org was removed from DNS again, as a short term workaround (not a pressing issue, though, so short term can become pretty long). Need to figure out what the problem was and fix it properly. It would be interesting to know whether https://01.org has the same problem - it uses a similar setup. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.

8 years, 10 months

1
1
0 / 0

[Bug 56524] New: PIM Manager: accent-insensitive search

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=56524 Priority: medium Bug ID: 56524 CC: syncevolution-issues(a)syncevolution.org Assignee: syncevolution-issues(a)syncevolution.org Blocks: 56141 Summary: PIM Manager: accent-insensitive search Severity: enhancement Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: unspecified Component: SyncEvolution Product: SyncEvolution Currently, searching can be case-insensitive and case-sensitive. The difference between characters with and without accent is still relevant, so "Muller" does not find "Müller". It could be useful to also ignore accents. One way to implement this might be: - decompose as NFKD - throw away characters which are modifiers or accents (exact filter to be decided) See: http://unicode.org/reports/tr15/#Norm_Forms -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

8 years, 10 months

1
4
0 / 0

[Bug 56334] New: PIM API: persistent selection of active databases

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=56334 Priority: medium Bug ID: 56334 CC: syncevolution-issues(a)syncevolution.org Assignee: patrick.ohly(a)intel.com Blocks: 56141 Summary: PIM API: persistent selection of active databases Severity: enhancement Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: unspecified Component: SyncEvolution Product: SyncEvolution The sort order is stored persistently, as defined in the PIM API. However, the selection of active databases is not stored. It should be stored, because otherwise the goal of storing the sort order (allow to start syncevo-dbus-server before the UI) is defeated (pre-loaded and sorted data will always be empty). -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 9 months

1
1
0 / 0

[Bug 56436] New: PIM API: avoid colon in peer UID

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=56436 Priority: medium Bug ID: 56436 CC: syncevolution-issues(a)syncevolution.org Assignee: patrick.ohly(a)intel.com Blocks: 55916 Summary: PIM API: avoid colon in peer UID Severity: normal Classification: Unclassified OS: All Reporter: patrick.ohly(a)gmx.de Hardware: Other Status: ASSIGNED Version: unspecified Component: SyncEvolution Product: SyncEvolution The API allowed colons as part of the peer UID. This special character is avoided in SyncEvolution config file names and thus currently gets replaced by underscores (SetPeer works, GetAllPeers returns different uid). Instead of trying to figure out how to support a colon in UID, better remove it from the API definition. -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 9 months

1
2
0 / 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Syncevolution-issues October 2012