| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
They are needed to build it
|
| |
|
|
|
|
| |
(cherry picked from commit 8b0ca6beb2878b0eaeaf95122125986dd1225f0a)
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/112
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Two issues:
a) when the server returns success on the given URL PROPFIND, but
doesn't support /.well-known/ addresses, then the try on the
/.well-known/ could overwrite the success of the given URL PROPFIND,
causing return failure without setting the GError;
b) when the given URL is a collection of the type the output is filtered
for, the URL could be skipped from consideration and not included
in the output discovered resources.
Reported downstream as a gnome-calendar crash:
https://bugzilla.redhat.com/show_bug.cgi?id=1287073
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/137
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Calling “x = g_string_append (x, y)” is equivalent to
“g_string (x, y)”. Or take it into account, when this leads
to shorter code.
Likewise for g_string_append_unichar().
Use the return value fo g_string_append(), when this makes
the code sherter.
In camel_content_disposition_format: skip a realloc() call.
In camel-sasl-ntlm.c: skip a g_string_append_len() call.
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/22
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/26
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/23
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/24
|
|
|
|
|
|
| |
When string->len == 4, the value of string->str was leaked.
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/20
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/19
|
|
|
|
|
|
| |
Likewise for g_string_prepend_c() and g_string_prepend().
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/18
|
| |
|
| |
|
|
|
|
|
| |
The first chunk to not clash with top-block variable of the same name.
The second to always return a new component instance on success.
|
| |
|
|
|
|
|
|
|
| |
The CamelOfflineStore did not reconnect once it disconnected, only
after whole CamelSession went offline and online.
Related to https://gitlab.gnome.org/GNOME/evolution/issues/479
|
|
|
|
|
| |
This way also latitude and longitude properties are provided. It also
makes the copied timezone more accurate to the built-in.
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/130
|
| |
|
| |
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/128
|
| |
|
| |
|
| |
|
|
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution/issues/479
|
| |
|
|
|
|
|
|
|
| |
The returned duration can be a _null_duration or a _bad_duration,
even when the returned ICalDuration object is not NULL.
Reported as part of the https://gitlab.gnome.org/GNOME/evolution/issues/484
|
|
|
|
|
| |
When a folder is fully synchronized for offline, any search can be done
with local data, without issuing SEARCH command on the server.
|
|
|
|
|
|
| |
As it was, when the store went online, it just connected, even the code
tried to do some things when going online, like synchronizing messages
for offline use. The change allows to do what was meant to be done.
|
| |
|
| |
|
|
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution/issues/476
|
| |
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/17
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/121
|
|
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution/issues/471
|
| |
|
|
|
|
|
|
| |
This is used for calendar backends referencing custom files and it allows
to tell the backend whether the calendar should be opened in writable way.
It doesn't force writable open for files which cannot be open in write mode.
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/123
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/108
|
| |
|
|
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/15
|
|
|
|
|
| |
Otherwise the window shows incorrect time until the first overdue
update is invoked in a timeout callback.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ECalBackendSExp usage could cause a deadlock when one thread
had been starting the view, while another thread had been notifying
existing views about created/modified/removed objects with the file
backend, which uses its internal lock within tzcache_get_timezone()
function. Exposing the Backend SExp lock into the public and locking
it before starting the view helps to avoid this deadlock.
Similar lock had been added to the EBookBackendSExp too.
The backtrace of the two threads follows:
Thread 2 (Thread 0x7f4735fab700 (LWP 11567)):
0 in syscall () at /lib64/libc.so.6
1 in g_mutex_lock_slowpath () at /lib64/libglib-2.0.so.0
2 in e_cal_backend_sexp_match_comp (sexp=0x7f47c80682a0, comp=comp@entry=0x7f47c0018920, cache=0x2c65b00)
at ..../src/calendar/libedata-cal/e-cal-backend-sexp.c
3 in match_object_sexp_to_component (value=0x7f47c0018920, data=0x7f4735faab40)
at ..../src/calendar/backends/file/e-cal-backend-file.c
4 in g_list_foreach () at /lib64/libglib-2.0.so.0
5 in e_cal_backend_file_start_view (backend=0x2c65b00, query=0x7f477c01a5b0)
at ..../src/calendar/backends/file/e-cal-backend-file.c
6 in calview_start_thread (data=0x7f477c01a5b0)
at ..../src/calendar/libedata-cal/e-data-cal-view.c
7 in g_thread_proxy () at /lib64/libglib-2.0.so.0
8 in start_thread () at /lib64/libpthread.so.0
9 in clone () at /lib64/libc.so.6
Thread 1 (Thread 0x7f4820dcba80 (LWP 5054)):
0 in __lll_lock_wait () at /lib64/libpthread.so.0
1 in _L_lock_941 () at /lib64/libpthread.so.0
2 in pthread_mutex_lock () at /lib64/libpthread.so.0
3 in cal_backend_file_get_cached_timezone (cache=0x2c65b00, tzid=0x2cbc790 "America/New_York")
at ..../src/calendar/backends/file/e-cal-backend-file.c
4 in func_occur_in_time_range (user_data=0x2cbab10, tzid=<optimized out>)
at ..../src/calendar/libedata-cal/e-cal-backend-sexp.c
5 in func_occur_in_time_range (esexp=0x2c4e100, argc=<optimized out>, argv=<optimized out>, data=0x2cbab10)
at ..../src/calendar/libedata-cal/e-cal-backend-sexp.c
6 in e_sexp_term_eval (sexp=sexp@entry=0x2c4e100, t=0x2c4a400)
at ..../src/libedataserver/e-sexp.c
7 in e_sexp_eval (sexp=0x2c4e100)
at ..../src/libedataserver/e-sexp.c
8 in e_cal_backend_sexp_match_comp (sexp=0x7f47c80682a0, comp=comp@entry=0x7f47c0018f20, cache=<optimized out>)
at ..../src/calendar/libedata-cal/e-cal-backend-sexp.c
9 in e_data_cal_view_component_matches (view=view@entry=0x7f477c01a5b0, component=component@entry=0x7f47c0018f20)
at ..../src/calendar/libedata-cal/e-data-cal-view.c
10 in e_cal_backend_notify_component_created (backend=<optimized out>, component=0x7f47c0018f20)
at ..../src/calendar/libedata-cal/e-cal-backend.c
11 in e_cal_backend_create_objects_finish (backend=0x2c65b00, result=result@entry=0x7f47f80648a0, out_uids=out_uids@entry=0x7fff7bd8d200, error=error@entry=0x7fff7bd8d1f8)
at ..../src/calendar/libedata-cal/e-cal-backend.c
12 in data_cal_complete_create_objects_cb (source_object=0x2c65b00, result=0x7f47f80648a0, user_data=0x2c31d80)
at ..../src/calendar/libedata-cal/e-data-cal.c
13 in g_simple_async_result_complete () at /lib64/libgio-2.0.so.0
14 in complete_in_idle_cb () at /lib64/libgio-2.0.so.0
15 in g_idle_dispatch () at /lib64/libglib-2.0.so.0
16 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
17 in g_main_context_iterate.isra.19 () at /lib64/libglib-2.0.so.0
18 in g_main_loop_run () at /lib64/libglib-2.0.so.0
19 in main (argc=1, argv=0x7fff7bd8d518)
at ..../src/calendar/libedata-cal/evolution-calendar-factory-subprocess.c
|
|
|
|
|
|
|
| |
Even with the previous commit there still could happen some issue
with D-Bus property change notifications, thus add a workaround to
the related book and calendar tests, because it's not a problem
on the evolution-data-server side, but somewhere deeper.
|
|
|
|
|
| |
This should make sure the client side will receive property changes
as soon as possible.
|