| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
When creating new messages the default should be that the full payload
is available. Not having the payload available is a specialcase used by
the imap resource.
|
| |
|
|
|
|
|
|
|
|
|
| |
Incremental additions of children in the tree were filtered due to the
parent filter. This broke when we started to maintain state, thus
causing the filter in datastorequery containing the parent filter to be
carried over. Given that the incremental querying of children currently
doesn't really add much value (we don't have trees that are large/deep
enough), perhaps we're better off using a different approach.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
corruption.
It looks like the memory corruption (malloc started to crash) was coming QLocalSocket related
signals. According to the docs it's not safe (whatever that means), to
delete a QObject with pending signals, so we use deleteLater to schedule
it's deletion. This resolved the crashes.
|
| |
|
|
|
|
|
|
| |
Doesn't work with CATCH_ERRORS=ON
This reverts commit 2bb2a10f5c4010d168b3d26e9937cf26365a0d0c.
|
| |
|
|
|
|
|
|
| |
Fixing this introduces some crashes. I'll have to revisit this.
This reverts commit 679f2d5d7d46b2f098e939883520b707f01b2a36.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Just truncating the file is not a good idea. If the headers end up being
larger (I just ran into that), then we just fail to parse the headers
and miss important stuff like subjects. So let's not.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|