The Netherlands
Comment by ~whynothugo on ~whynothugo/vdirsyncer-rs
Comment by ~whynothugo on ~whynothugo/vdirsyncer-rs
Even with the above, we should probably only use a default if the default configuration path was used, to avoid accidental mix-ups.
Ticket created by ~whynothugo on ~whynothugo/vdirsyncer-rs
When creating a plan, find any stale mappings and add actions to flush them.
Comment by ~whynothugo on ~whynothugo/vdirsyncer-rs
Hugo Osvaldo Barrera referenced this ticket in commit 92f2c19.
REPORTED
RESOLVED FIXEDComment by ~whynothugo on ~whynothugo/vdirsyncer-rs
Thanks for reporting this, it was a silly oversight.
Comment by ~whynothugo on ~whynothugo/vdirsyncer-rs
Hugo Osvaldo Barrera referenced this ticket in commit a8b9461.
REPORTED
RESOLVED FIXEDComment by ~whynothugo on ~whynothugo/vdirsyncer-rs
I have a fix, will push it later today / tomorrow.
Comment by ~whynothugo on ~whynothugo/vdirsyncer-rs
I found out the issue: when planning, we use
get_many_items
to fetch all items in a single HTTP request.When actually executing the plan, items are fetched one by one, which results in one HTTP request for each item (but all requests re-fetch the same file).
I should keep the fetched data after planning and avoid re-fetching.
0:bug added by ~whynothugo on ~whynothugo/vdirsyncer-rs
Comment by ~whynothugo on ~whynothugo/vdirsyncer-rs
You're not using debug builds (which is the default, right?)