mirror of
https://github.com/photoprism/photoprism.git
synced 2026-03-02 22:57:18 -05:00
Logs: Vision caption thumbnail returns wrong error variable #2464
Labels
No labels
ai
android
api
auth
awesome
bug
bug
ci
cli
config
database
declined
deprecated
docker
docs 📚
documents
duplicate
easy
enhancement
enhancement
enhancement
epic
faces
feedback wanted
frontend
hacktoberfest
help wanted
idea
in-progress
incomplete
index
invalid
ios
labels
live
live
low-priority
macos
member-feature
metadata
mobile
nas
needs-analysis
no-coding-required
no-coding-required
observability
performance
places
please-test
plus-feature
priority
pro-feature
question
raspberry-pi
raw
released
released
released
research
resolved
security
sharing
tested
tests
third-party-issue
thumbnails
upgrade
upstream-issue
ux
vector
video
waiting
won't fix
won't fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/photoprism#2464
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dyptan-io on GitHub (Dec 27, 2025).
Originally assigned to: @graciousgrey, @dyptan-io on GitHub.
Before You Continue
What Is Not Working as Documented?
When vision generates caption thumbnails for specific media (corrupted media in my example), it crashes due to the wrong error variable being returned.
How Can We Reproduce It?
Run against media that cannot generate a thumbnail, like corrupted files?
What Behavior Do You Expect?
The program logs the error and continues with the remaining media instead of crashing with panic.
What Could Be the Cause?
Likelly a bug in the following code:
Logs, Sample Files, or Screenshots
Which Software Versions Do You Use?
On What Device Is PhotoPrism Installed?
Do You Use a Reverse Proxy, Firewall, VPN, or CDN?
No response
@lastzero commented on GitHub (Dec 29, 2025):
@dyptan-io Thanks for reporting this glitch! After reviewing the code, I discovered two more instances where the wrong error variable was used. You'll soon be able to test the fixes using our development preview build:
@lastzero commented on GitHub (Feb 11, 2026):
We have updated our preview build to include fixes for this issue and several others:
It would be great if you could test it and provide feedback! :)