Skip to content

v82.0.7579.33985 (**unpublished**)

Pre-release
Pre-release
Compare
Choose a tag to compare
@GerHobbelt GerHobbelt released this 01 Nov 19:38
· 721 commits to master since this release
v82.0.7579.33985
0bc6d6d

A quick preliminary installer produced, mainly for jimmejardine#257 and jimmejardine#264 while the Sync rework needs to be completed so users can finally change the Sync Point for any library.

The most important changes in this one are:

  • several additions towards recognizing and recovering botched/corrupted library databases, both local (*.library) and at Sync Point (*.s3db)

  • SQLite database errors are of critical importance to the functioning of Qiqqa: when an SQLite error occurs, a diagnostic report is appended in the log files. This info includes all available File System information and a quick analysis & test of the accessibility / readability of the DB file.

    This should help us diagnose otherwise obscure problems like jimmejardine#257 and jimmejardine#264

  • wholesale refactor of some internals which should improve memory management and reduce bugs, at least in the long term. (commit jimmejardine@0d35bf6)

    While a number of bugs have been thwarted this way, I still cannot guarantee that you won't see a few 'null reference' errors being reported with this version.

    I haven't had time to kill them all, because removing those error reports also makes it much harder for me to diagnose WHY this erroneous result happens and what the underlying issue is, which SHOULD be fixed. In other words: silencing Qiqqa right now will severely reduce my chances to observe graver, underlying, errors and fix those, as those will become harder to spot and report.

  • various integrity checks have been added and any findings will be reported in the log files.

  • tested against a slew of v76-v79 commercial Qiqqa databases in various states of disrepair: this version will cope better with those than any previous Qiqqa release and 'recover' more data.

IMPORTANT NOTE on the 'recover' words above:

Qiqqa currently 'recovers' such databases in that it attempts to load them as best it can, repair the gaps if finds and has redundant data for, but the original database files ARE NOT rewritten, hence these errors will recur on every application start.

A future Qiqqa release will include an option to bulk-copy PDFs and metadata from such damaged libraries to a fresh one as a form of real recovery process. Ditto for metadata gathering for PDFs which have no metadata attached, but whose metadata MAY be found in a alternate library -- giving you the ability to recover from hard library failures from arbitrary backups.

Status: Unpublished?

  • this is an unpublished release as the now visible links and popup menu items for library edit & delete are still non-functional.
  • the second reason being that you will currently be informed of damaged libraries, but have not easy means to really recover. See the notes further above.

Qiqqa now knows only about three (or rather: two) types of libraries:

  1. regular libraries, including the default/guest library
  2. Intranet libraries -- which are the regular libraries that have a known Sync Point a.k.a. Share Target directory. This can be observed in the Sync Manager dialog.
  3. Bundle libraries -- which remain read-only as before.

See also the CHANGELOG (and the CHANGELOG_FULL for a complete report.

Assets 3