Commit message (Collapse) | Author | Age | ||
---|---|---|---|---|
... | ||||
* | | Allow the preprocessor to move and use in mailtransport | Christian Mollekopf | 2017-04-12 | |
| | | ||||
* | | Moved all preprocessing back into the pipeline | Christian Mollekopf | 2017-04-11 | |
| | | ||||
* | | Move the preprocssing back out of entitystore into the pipeline. | Christian Mollekopf | 2017-04-11 | |
| | | | | | | | | | | This is where this really belongs, only the indexing is part of storage. This is necessary so preprocessors can move entities as well. | |||
* | | We set the instance identifier in the base class | Christian Mollekopf | 2017-04-11 | |
| | | ||||
* | | Less noise | Christian Mollekopf | 2017-04-10 | |
| | | ||||
* | | Don't continue processing the pipeline until we have appended the | Christian Mollekopf | 2017-04-10 | |
| | | | | | | | | | | | | message. Otherwise the processor might think its done before it actually is. | |||
* | | Added uid index | Christian Mollekopf | 2017-04-10 | |
| | | ||||
* | | Fixed readAllUids and readAll | Christian Mollekopf | 2017-04-10 | |
| | | ||||
* | | Send an error status messagebefore crashing. | Christian Mollekopf | 2017-04-07 | |
| | | ||||
* | | Detect maildir resource errors | Christian Mollekopf | 2017-04-07 | |
| | | ||||
* | | Better account status aggregation. | Christian Mollekopf | 2017-04-07 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Only ever enter error state on non-recoverable errors. Otherwise: * Busy state while busy, then go back to online/offline/error. * If we failed connect during replay/sync we assume we're offline. * If we failed to login but could connect we have a known error condition. * If we succeeded to replay/sync something we are apprently online. At the core we have the problem that we have no way of telling wether we can connect to the server until we actually try (network is not enough: vpns, firewalls, ....). Further the status always reflects the latest status, so even if we were in an error state, once we retry we go out of the error state and either end up back in the error state or not. When aggregating states we have to similarly adjust the state to the most relevant among the resources. The states are ordered like this: * Error * Busy * Connected * Offline | |||
* | | Be less verbose | Christian Mollekopf | 2017-04-07 | |
| | | | | | | | | We already see the resource exiting. | |||
* | | Fixed changereplay guard | Christian Mollekopf | 2017-04-06 | |
| | | | | | | | | ...and improved debug output slightly. | |||
* | | Mailtransport notifications | Christian Mollekopf | 2017-03-30 | |
| | | ||||
* | | Print notification type names | Christian Mollekopf | 2017-03-29 | |
| | | ||||
* | | Emit dataChanged without roles | Christian Mollekopf | 2017-03-29 | |
| | | ||||
* | | Cleanup | Christian Mollekopf | 2017-03-28 | |
| | | ||||
* | | Added missing property mappers | Christian Mollekopf | 2017-03-28 | |
| | | ||||
* | | Guard against destruction | Christian Mollekopf | 2017-03-28 | |
| | | | | | | | | We really need to guard against this in kasync... | |||
* | | Don't filter trash in the standard query | Christian Mollekopf | 2017-03-28 | |
| | | | | | | | | ...we selectively apply the filter in kube instead. | |||
* | | Only send notifications about being connected if we did something | Christian Mollekopf | 2017-03-28 | |
| | | | | | | | | | | | | against the source. We used to replay no changes and then claim the resource was online. | |||
* | | Track the entities that this request applies to directly in the | Christian Mollekopf | 2017-03-28 | |
| | | | | | | | | | | | | | | | | syncrequest That way we can do the notification emitting in the synchronizer and it keeps working even if the login already fails (so the synchronizing code would never be executed). | |||
* | | Don't use 0 as error code and better error codes | Christian Mollekopf | 2017-03-27 | |
| | | ||||
* | | Fixed notification quering | Christian Mollekopf | 2017-03-26 | |
| | | ||||
* | | Don't filter notifications too early. | Christian Mollekopf | 2017-03-26 | |
| | | | | | | | | | | | | With this it becomes difficult to test notifications, and notifications may contain more interesting information, so we don't want to drop them too early. | |||
* | | Test the result of the write operation. | Christian Mollekopf | 2017-03-26 | |
| | | ||||
* | | Use the resourceaccessfactory for notifiers as well. | Christian Mollekopf | 2017-03-26 | |
| | | | | | | | | | | Otherwise we end up trying to start the resource from multiple places in notifiertest. | |||
* | | Implemented notification support in the model. | Christian Mollekopf | 2017-03-24 | |
| | | | | | | | | | | | | | | | | This will allow us to fold things like progress and sync status directly into the model. Usecases are mail download progress and folder sync progress. Ideally we would also solve the resource/account state through this. | |||
* | | Fixed identity name | Christian Mollekopf | 2017-03-24 | |
| | | ||||
* | | DomainType::name | Christian Mollekopf | 2017-03-23 | |
| | | ||||
* | | New properties | Christian Mollekopf | 2017-03-23 | |
| | | ||||
* | | Maintain the query state instead of using the offset. | Christian Mollekopf | 2017-03-22 | |
| | | | | | | | | | | | | | | | | | | | | Instead of using the offset to skip over old results requires recalculating them, and resulted in some cases in results being added multiple times to the model. By just maintaining the state we can apply the offset directly to the base-set, and maintain the state in reduction etc. which is necessary to continue streaming results while making sure we don't report anything twice. | |||
* | | Default domain adaptor | Christian Mollekopf | 2017-03-21 | |
| | | ||||
* | | Move type implementations in one place | Christian Mollekopf | 2017-03-21 | |
| | | | | | | | | | | | | | | Having them separated is rather pointless (since we need one for every type, and all types are the interface of sink, as one), and caused quite a bit of friction when adding new types. This will also make it easier to change things for all types. | |||
* | | Better debugoutput | Christian Mollekopf | 2017-03-21 | |
| | | ||||
* | | Make error codes part of the applicationdomain interface | Christian Mollekopf | 2017-03-20 | |
| | | ||||
* | | We need the resource filter API also for SyncScope | Christian Mollekopf | 2017-03-19 | |
| | | ||||
* | | Better error message | Christian Mollekopf | 2017-03-19 | |
| | | ||||
* | | Excluded trash from threadleaders. | Christian Mollekopf | 2017-03-19 | |
| | | ||||
* | | Handle filtered thread-leader | Christian Mollekopf | 2017-03-19 | |
| | | ||||
* | | Removed unnecessary debug output | Christian Mollekopf | 2017-03-18 | |
| | | ||||
* | | emitNotification function | Christian Mollekopf | 2017-03-17 | |
| | | ||||
* | | Added notification code for mailtransport | Christian Mollekopf | 2017-03-17 | |
| | | ||||
* | | Preparation to get useful notifications to Kube | Christian Mollekopf | 2017-03-15 | |
| | | ||||
* | | Fixed warnings | Christian Mollekopf | 2017-03-15 | |
| | | ||||
* | | Fixed specialpurpose preprocessor | Christian Mollekopf | 2017-03-15 | |
| | | | | | | | | Set the flags on new mail as well | |||
* | | Improve log context identifier | Christian Mollekopf | 2017-03-14 | |
| | | | | | | | | | | We already set the resource id for the resource process, so adding it again really adds nothing at all. | |||
* | | Always request properties we use and in turn avoid getting errors | Christian Mollekopf | 2017-03-14 | |
| | | | | | | | | | | ...by setting dummy values for properties we do not actually have set in the config. | |||
* | | Debug output | Christian Mollekopf | 2017-03-14 | |
| | | ||||
* | | An error should not stop the synchronizer from processing. | Christian Mollekopf | 2017-03-14 | |
| | |