- 16 Jun, 2016 2 commits
-
-
Laurent Montel authored
-
Laurent Montel authored
-
- 12 Jun, 2016 1 commit
-
-
Laurent Montel authored
-
- 05 Jun, 2016 3 commits
-
-
Daniel Vrátil authored
Use ${QtSql_PRIVATE_INCLUDE_DIRS} to include the private headers directly from current Qt install instead of carrying a local copy.
-
Daniel Vrátil authored
The GidTest needs to retrieve item payload from the resource, so we need the resources to be online for that, otherwise the tests timeouts.
-
Daniel Vrátil authored
This test needs the resources to be online for remote search test.
-
- 04 Jun, 2016 5 commits
-
-
Daniel Vrátil authored
Because why not
-
Daniel Vrátil authored
-
Daniel Vrátil authored
C++11 is now provided by ECM, ASAN is set in CI. All the Qt definitions come from ECM now.
-
Daniel Vrátil authored
-
Daniel Vrátil authored
The CI only shows debug output from the test itself, but that is often not enough to find out what went wrong when the test fails. This enabled full debug output for everything inside the testrunner environment.
-
- 02 Jun, 2016 2 commits
-
-
Nicolás Alvarez authored
- I already found what I wanted to know - Putting the message() in this particular place made it be printed like 20 times. This reverts commit 84326213.
-
Nicolás Alvarez authored
I'm debugging why this works on the CI when it seems it shouldn't...
-
- 31 May, 2016 6 commits
-
-
Daniel Vrátil authored
-
Daniel Vrátil authored
I wasn't able to reproduce locally, but on CI we were hitting the newly added assert when receiving response after the job said it does not expect any more response. The server will send either one FetchTags or one DeleteTag response followed by ModifyTags response.
-
Daniel Vrátil authored
-
Daniel Vrátil authored
First debug, then assert, so we know more about why we asserted.
-
Laurent Montel authored
-
Laurent Montel authored
FIXED-IN: 5.2.2 BUG: 358696
-
- 30 May, 2016 6 commits
-
-
Daniel Vrátil authored
During DB initialization when multiple resources try to synchronize and insert first item, the mimetypes, parttypes and other similar tables are empty and the entries need to be created. This presents a race condition when multiple threads try to create the new entry at the same time - one of them is succesfull, the others usually abort, which leads to the resource failing the synchronization. retrieveByNameOrCreate() will try to retrieve the item from cache or DB first. If it does not get any result it tries to acquire a lock. If the thread gets a lock it inserts the new entry into DB and cache. Otherwise the thread just waits for the lock (i.e. until the thread that acquired the lock inserts the new entity) and then retrieves the entity from the cache. This isn't really a common situation, which would happen during normal usage of Akonadi. We however see it quite often during unit-test initialization when all three Knut resources start pushing their data into Akonadi at the same time and trigger this race condition.
-
Daniel Vrátil authored
-
Daniel Vrátil authored
This affects mostly CollectionSync, which would emit result() signal while a CommitTransaction subjob was still running. This caused the response to the CommitTransaction to be delivered to subsequent job started after the CollectionSync and was causing all kinds of havoc (like CollectionFetchJob emitting result() twice - once because of the CommitTransaction response not addressed to it and second time once the actual CFJ response arrived) in both clients and resources.
-
Daniel Vrátil authored
The CollectionCopyJob was expecting CreateCollection response instead of CopyCollection, causing it to trigger warning every time. Luckily no harm done there, since the job does not expect the Response to contain any data and only takes it as an indicator of result.
-
Laurent Montel authored
-
Laurent Montel authored
-
- 29 May, 2016 1 commit
-
-
Maximiliano Curia authored
-
- 27 May, 2016 1 commit
-
-
Maximiliano Curia authored
As it was it randomly tried to build agenttype.cpp before generating the controlinterface.h file. A full failing build log can be found in: http://freak.gnuservers.com.ar/~maxy/share/akonadi_failed_consoleText.txt The fix was proposed and approved by bshah via irc.
-
- 26 May, 2016 3 commits
-
-
David Faure authored
-
David Faure authored
Not sure how this happened, but I had akonadiserver use 100% CPU because of this while() loop, given that waitForReadyRead() returns immediately if the socket is in UnconnectedState. (cherry picked from commit 1b78ff45)
-
David Faure authored
This happened with large fonts and small icons - e.g. by forcing the font DPI on a Hi-DPI display. I just enlarge the text to encompass the whole item, which assumes that the icon is vertically centered, but I think that's a safe assmuption. (cherry picked from commit 124998fa)
-
- 22 May, 2016 5 commits
-
-
Daniel Vrátil authored
-
Daniel Vrátil authored
Most users don't have some logging categories enabled by default, or might have manually disabled them through QT_LOGGING_RULES or QT_LOGGING_CONF environment vars. Starting Akonadi with --verbose switch (akonadictl start --verbose) will override the Qt category filter and will enable all debug and warning messages. This is mostly for convenience, as it's easier to tell users in bugzilla to run akonadictl --verbose than how export QT_LOGGING_RULES properly.
-
Daniel Vrátil authored
-
Daniel Vrátil authored
On most distros PostgreSQL is installed in /usr/lib/postgresql/X.Y/ (where X.Y is the version of the server). Constantly manually updating the internal list of all possible versions does not really scale, so instead the code now lists all folders in /usr/lib/postgresql/, sorts it in descending order and then looks for the first folder that contains pg_ctl.
-
Daniel Vrátil authored
This implements support for various versions of Oracle MySQL and MariaDB, adding a special case for MySQL >= 5.7.4 (which removed --force command line option) and MySQL >= 5.7.6 (which deprecated mysql_db_install and recommends mysqld --initialize instead) Also improves debug output during initialization. BUG: 361485 FIXED-IN: 16.04.2
-
- 17 May, 2016 1 commit
-
-
David Faure authored
("Akonadi::ConnectionThread::dataReceived: Invalid command, the world is going to end!") Suggested and approved by Dan.
-
- 16 May, 2016 2 commits
-
-
David Faure authored
Not sure how this happened, but I had akonadiserver use 100% CPU because of this while() loop, given that waitForReadyRead() returns immediately if the socket is in UnconnectedState.
-
David Faure authored
This happened with large fonts and small icons - e.g. by forcing the font DPI on a Hi-DPI display. I just enlarge the text to encompass the whole item, which assumes that the icon is vertically centered, but I think that's a safe assmuption.
-
- 15 May, 2016 2 commits
-
-
Daniel Vrátil authored
-
Daniel Vrátil authored
We don't enable NO_ZERO_DATE by default, but external servers may be configured to use it and will fail to create the PimItemTable in such case. Having a default time on atime makes no difference since we already explicitly set atime to QDateTime::currentDateTime() in the code when appending a new PimItem. BUG: 362580 FIXED-IN: 16.04.2
-