Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Avoid messageId related warnings | Christian Mollekopf | 2018-01-03 |
| | |||
* | Removed broken tests | Christian Mollekopf | 2018-01-03 |
| | |||
* | Removed unused synclistresult | Christian Mollekopf | 2018-01-02 |
| | |||
* | No parent query | Christian Mollekopf | 2018-01-02 |
| | |||
* | Avoid ending up with a connection lost error when a select fails | Christian Mollekopf | 2018-01-02 |
| | |||
* | Going towards 0.6 | Christian Mollekopf | 2017-12-30 |
| | |||
* | Prepared release of v0.5.0HEADv0.5.0master | Christian Mollekopf | 2017-12-30 |
| | |||
* | Change the default for fullPayloadAvailable | Christian Mollekopf | 2017-12-29 |
| | | | | | | 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. | ||
* | Fixed removal of entity | Christian Mollekopf | 2017-12-29 |
| | |||
* | Avoid the date limit for tests. | Christian Mollekopf | 2017-12-28 |
| | |||
* | Cleanup | Christian Mollekopf | 2017-12-28 |
| | |||
* | Fixed incremental updates in folder queries | Christian Mollekopf | 2017-12-28 |
| | | | | | | | | | 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. | ||
* | Fixed log pattern matching | Christian Mollekopf | 2017-12-28 |
| | |||
* | Backwardscompatibility for existing settings. | Christian Mollekopf | 2017-11-28 |
| | |||
* | Fixed imap tests | Christian Mollekopf | 2017-11-28 |
| | | | | Adjust to cyrus imap settings and use explicit encryption setting. | ||
* | Adjust testscript paths to new dockercontainer | Christian Mollekopf | 2017-11-23 |
| | |||
* | Check for errors | Christian Mollekopf | 2017-11-23 |
| | |||
* | Print transaction span | Christian Mollekopf | 2017-11-21 |
| | |||
* | Storage debugging code | Christian Mollekopf | 2017-11-21 |
| | |||
* | Print key/value when put fails | Christian Mollekopf | 2017-11-20 |
| | |||
* | Dump key and value sizes on inspect | Christian Mollekopf | 2017-11-17 |
| | |||
* | Removed ResourceAccess::Private leak and resolved resulting memory | Christian Mollekopf | 2017-11-16 |
| | | | | | | | | | 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. | ||
* | Added timeouts to sinkloadtest | Christian Mollekopf | 2017-11-15 |
| | |||
* | Ensure the flatbuffer file is built before the tests | Christian Mollekopf | 2017-11-14 |
| | |||
* | lsan suppressions | Christian Mollekopf | 2017-11-14 |
| | |||
* | Fixed use after free | Christian Mollekopf | 2017-11-14 |
| | |||
* | qrand is leaking it seems? | Christian Mollekopf | 2017-11-14 |
| | | | | perhaps just not properly instrumented. | ||
* | Fixed leak | Christian Mollekopf | 2017-11-13 |
| | |||
* | Suppress the known ResourceAccess leak | Christian Mollekopf | 2017-11-12 |
| | |||
* | lsan leak suppressions | Christian Mollekopf | 2017-11-12 |
| | | | | | | We get a lot of known "leaks" from lmdb. Some are willingly (we never close the environment and dbi's), others are likely because lmdb itself is not instrumented. | ||
* | Remove complete commands from the completeCommands hash again | Christian Mollekopf | 2017-11-12 |
| | |||
* | Revert "Fixed warnings" | Christian Mollekopf | 2017-11-12 |
| | | | | | | Doesn't work with CATCH_ERRORS=ON This reverts commit 2bb2a10f5c4010d168b3d26e9937cf26365a0d0c. | ||
* | Got rid of the AVOID_BINDING_REBUILD hack. | Christian Mollekopf | 2017-11-12 |
| | | | | | This new solution should provide decent rebuild times without special treatment. | ||
* | Fixed warnings | Christian Mollekopf | 2017-11-11 |
| | |||
* | Fixed warnings | Christian Mollekopf | 2017-11-10 |
| | |||
* | Revert "Fixed memoryleak" | Christian Mollekopf | 2017-11-10 |
| | | | | | | Fixing this introduces some crashes. I'll have to revisit this. This reverts commit 679f2d5d7d46b2f098e939883520b707f01b2a36. | ||
* | TSAN | Christian Mollekopf | 2017-11-10 |
| | |||
* | Fixed use after free | Christian Mollekopf | 2017-11-09 |
| | |||
* | Fixed memoryleak | Christian Mollekopf | 2017-11-09 |
| | |||
* | Fixed memoryleak | Christian Mollekopf | 2017-11-09 |
| | |||
* | ASAN support | Christian Mollekopf | 2017-11-09 |
| | |||
* | Require valgrind when enabling memcheck | Christian Mollekopf | 2017-11-07 |
| | |||
* | We rely on not defining template functions | Christian Mollekopf | 2017-11-03 |
| | | | | ...because we manually insantiate them in the cpp file. | ||
* | Fixed warning | Christian Mollekopf | 2017-11-03 |
| | |||
* | Benchmarks in tests are too fragile | Christian Mollekopf | 2017-11-03 |
| | |||
* | sinkloadtest.py | Christian Mollekopf | 2017-11-03 |
| | |||
* | Livequery | Christian Mollekopf | 2017-11-03 |
| | |||
* | Ensure we get a return code | Christian Mollekopf | 2017-11-01 |
| | |||
* | Ensure we get an appropriate exit code when a resource crashes. | Christian Mollekopf | 2017-10-31 |
| | |||
* | Sink clear error message | Christian Mollekopf | 2017-10-26 |
| |