asonix/pict-rs
1
1
Fork 1
Code Issues 2 Pull requests 3 Actions Projects Releases 133 Wiki Activity
pict-rs/releases/0.5.10.md
asonix 5f850f8c86
All checks were successful
/ check (aarch64-unknown-linux-musl) (push) Successful in 2m57s
Details
/ check (armv7-unknown-linux-musleabihf) (push) Successful in 2m55s
Details
/ check (x86_64-unknown-linux-musl) (push) Successful in 2m13s
Details
/ tests (push) Successful in 2m28s
Details
/ clippy (push) Successful in 1m22s
Details
/ publish-docker (push) Successful in 31s
Details
/ publish-forgejo (push) Successful in 21s
Details
/ publish-crate (push) Successful in 2m29s
Details
/ build (map[artifact:linux-amd64 platform:linux/amd64 target:x86_64-unknown-linux-musl]) (push) Successful in 6m23s
Details
/ build (map[artifact:linux-arm32v7 platform:linux/arm/v7 target:armv7-unknown-linux-musleabihf]) (push) Successful in 6m29s
Details
/ build (map[artifact:linux-arm64v8 platform:linux/arm64 target:aarch64-unknown-linux-musl]) (push) Successful in 6m24s
Details
Prepare 0.5.10 release
2024-03-23 18:59:48 -05:00

1.1 KiB
Raw Blame History

pict-rs 0.5.10

Overview

pict-rs 0.5.10 is a small release with changes to how pict-rs handles temporary files.

Changes

Upgrade Notes

There are no significant changes from 0.5.9. Upgrading should be as simple as pulling the new version.

Descriptions

Temporary File Cleanup

pict-rs now nests its temporary files inside a pict-rs toplevel temporary folder. This is useful because pict-rs 0.5.10 introduces a new behavior: it will completely delete that folder and its contents on launch. If you are running multiple copies of pict-rs on the same host and they share your temporary folder, this might cause problems. In that scenario, this behavior can be disabled by setting PICTRS__SERVER__CLEANUP_TEMPORARY_DIRECTORY=false or passing --no-cleanup-temporary-directory on the commandline.

This new behavior has been introduced in order to better clean up after crashes. If pict-rs is killed while processing media, maybe due to an OOM, it will leave files behind in the temporary directory. This can cause the temporary directory to grow, leading to memory or disk problems.