Community
Participate
Working Groups
After an unexptected close it could be that the stored data is corrupt (e.g. while checking out from a remote-rep, or saving data). This corrupt data needs to be identified by the default build of a project (after a crash a build is scheduled) and corrupted data needs to be restored (if possible from local history) or deleted. The following usecases are affected: * Loading an information unit * Loading the project-structure * Loading the cached tags * Loading the remote repository-store * Loading rulesets * Loading the sections of the desktop-panel.