Angaben zum Datum
Datum aus der Quelle.
Erstmals gesehen am .
Karakeep 0.33.2: Fehlerbehebungen und neues Chrome-Container-Image
Karakeep 0.33.2 behebt mehrere Fehler: "use max completion tokens" ist bei der Standard-OpenAI-Konfiguration nun standardmäßig true, große singlefile-Archive mit Videos lassen sich wieder per Metadaten-Extraktion verarbeiten, die Asset-Konvertierung im Crawler wurde abgesichert und nodejs ist auf 24.18.1 festgelegt, außerdem wird ein neues eigenes Chrome-Container-Image (Chrome 151 statt 124) empfohlen, während das alte weiterhin funktioniert.
0.33.2
This is a patch release for after 0.33.1. It contains the following fixes:
Bug fixes:
- Change default "use max completion tokens" token env variable to
truewhen using the default OpenAI configuration now that we're using 5.6 luna and this flag is required there (#3007). - We're migrating to a custom karakeep chrome container (based on https://github.com/chromedp/docker-headless-shell) now that the old alpine-chrome is no longer fetch-able (and has been long abandoned by the maintainer). Check the migration guide here. The old image will continue to work, but it's recommended that you migrate to the new one as it also upgrades chrome to 151 (compared to 124 in the old image). If you've been using browserless (e.g. on unraid), you're not impacted by this, and you don't need to migrate.
- Large singlefile archives (typically because of videos) used to fail metadata extraction as the parser used to OOM. We strip inline videos now to make the parsing succeed.
- Hardened the link to asset conversion mechanism in the crawler that used to result into silently broken assets. (#3002)
- Pinned nodejs to version 24.18.1 thanks to @eriktews (#2996) to overcome a bug in the latest node 24.19 version (check #2989 for details). The proxmox scripts also were pinned by @MickLesk. …