| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This brings the incremental closer to a regular query (about 1.5 times
as bad instead of 3.5 times).
For a comparison look at MailQueryBenchmark::testIncremental()
The optimization is built on the assumption that we i.e. get an update
with 100 revisions, and thus the optimization applies to the case where
we have multiple revisions within that batch that are part of the same
reduction. In such a case we can avoid redoing the reduction lookup over
and over.
|
| |
|
|
|
|
| |
We run into a crash otherwise when creating the first account..
|
|
|
|
|
|
|
| |
The password (or any other secret), is now cached in the client process
(in-memory only), and delivered to the resource via command.
The resource avoids doing any operations against the source until the
secret is available.
|
| |
|
|
|
|
|
| |
We don't need an update for every mail if we download 50k mails. We just
need enough to animate a progress bar.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We used to simply return all uids.
Requires "sinksh upgrade"
|
| |
|
|
|
|
|
|
| |
after the query.
This fixes status monitoring when creating a new account.
|
|
|
|
|
| |
This resolves the following warning on shutdown it seems:
"QObject::connect: No such signal QObject::aboutToClose() in ../../include/QtCore/5.9.1/QtCore/private/../../../../../src/corelib/io/qtextstream_p.h:75"
|
|
|
|
|
|
| |
local static initialization is only threadsafe if initialized on
construction. The other codepath is not threadsafe, but is only used in
testcode.
|
| |
|
|
|
|
| |
In an attempt to resolve T6890.
|
|
|
|
| |
kimap should really have better error codes...
|
| |
|
|
|
|
|
|
| |
This allows the aggregation to ignore resources where we don't have any
status information yet, so the account doesn't always end up being
offline.
|
| |
|
|
|
|
|
| |
It can happen that thread messages are not delivered in order, which
means we will have to merge threads once all messages are available.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
setFuture can emit signals directly if the future is already stopped.
This does not apply to our case but it fixes the warning.
"QFutureWatcher::connect: connecting after calling setFuture() is likely to produce race"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From Qt's documentation: "This macro is obsolete. Use
target_link_libraries with IMPORTED targets instead." It's only
recommended with cmake >=2.8.9 & < 2.8.12. Sink already requires
cmake 3.0. One advantage of using the imported targets is, that
cmake complains if a target isn't found before it's used, like
Qt5Concurrent missing from the find_package_call here.
Reviewers: #sink, cmollekopf
Reviewed By: #sink, cmollekopf
Subscribers: #sink
Tags: #sink
Differential Revision: https://phabricator.kde.org/D6361
|
| |
|
| |
|
|
|
|
|
|
| |
This allows us to i.e. blindly mark mails as read in kube, with the
modification automatically being dropped if it doesn't do anything
useful.
|
| |
|
| |
|
|
|
|
| |
The while loop is executed at least once, so advanced is always true.
|
| |
|
| |
|
|
|
|
|
| |
Otherwise we end up sending sync requests for contacts to imap
resources.
|
| |
|
|
|
|
| |
Necessary to get notifications for newly created resources.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
We could do some event compression with a timer if necessary, but for
the time being we'll just flush after every notification.
This is necessary so i.e. a mail in the outbox appears immediately as it
is created in the resource.
|
|
|
|
|
|
| |
There's a new template version that expects methods that QByteArray
doesn't have but breaks the implicit conversion to const char *,
std::string is safer anyways (doesn't require a null terminated string).
|
| |
|
| |
|
|
|
|
|
| |
It seems to do more harm than good, creating huge threads,
and the webclient doesn't do it either.
|
|
|
|
|
|
| |
The incremental querying broke as soon as a revision update came in
since it would nuke the base-set. This fixes it, but it's definitely not
pretty.
|