• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

thumbor / thumbor / 42535897324
93%

Build:
DEFAULT BRANCH: master
Ran 08 Nov 2026 11:38PM UTC
Jobs 5
Files 105
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

08 Nov 2026 11:35PM UTC coverage: 92.527% (+0.4%) from 92.127%
42535897324

push

github

marcelometal
feat: add thumbor-cleanup to purge expired file storage entries

The file storage and the file result storage only ignore expired files, so
anything that is not requested again stays on disk forever. thumbor-cleanup
walks FILE_STORAGE_ROOT_PATH and RESULT_STORAGE_FILE_STORAGE_ROOT_PATH and
deletes regular files older than the configured expiration plus a grace
period, and it only reports them unless --delete is given. It reads the
configuration the way the server does, --use-environment included. In the
storage root it only touches files shaped like the ones the file storage
writes, removes detector files with their image, drops orphaned ones and
keeps the blacklist, which is configuration, not cache; in both roots it
removes leftover temporary files, even with the expiration disabled. Both
storages now treat a file that disappears while they read it, including the
security key, as missing instead of raising.

Uploads share the storage root and its expiration and cannot be told apart
on disk, so --storage refuses to run without --include-uploads when uploads
go to the file storage, directly or through the mixed storage. A None or
zero expiration deletes no image, although the file storage reads zero as
everything expired. Security key files are kept while
STORES_CRYPTO_KEY_FOR_EACH_IMAGE is on: thumbor never expires them and they
validate URLs signed before SECURITY_KEY changed, which would answer 400
once the key went away with its image. Each file is checked again right
before its unlink, so only one stored again in between can still be lost.
Links inside a root are never followed, a symlinked root is cleaned at its
target, and directories are kept to avoid racing writes.

285 of 285 new or added lines in 3 files covered. (100.0%)

4866 of 5259 relevant lines covered (92.53%)

4.63 hits per line

Jobs
ID Job ID Ran Files Coverage
1 run-3.15 - 42535897324.1 08 Nov 2026 11:38PM UTC 105
92.53
GitHub Action Run
2 run-3.14 - 42535897324.2 08 Nov 2026 11:38PM UTC 105
92.53
GitHub Action Run
3 run-3.11 - 42535897324.3 08 Nov 2026 11:38PM UTC 105
92.53
GitHub Action Run
4 run-3.13 - 42535897324.4 08 Nov 2026 11:38PM UTC 105
92.53
GitHub Action Run
5 run-3.12 - 42535897324.5 08 Nov 2026 11:38PM UTC 105
92.53
GitHub Action Run
Source Files on build 42535897324
  • Tree
  • List 105
  • Changed 2
  • Source Changed 2
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #42535897324
  • c961b4d7 on github
  • Prev Build on master (#42535503635)
  • Next Build on master (#43631838985)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc