The marker form already permits end == start, so refusing to render in
the generator was an inconsistent gate. Treat non-positive intervals the
same as a missing end (fall back to markerPreviewDefaultDuration) while
keeping the warning log for visibility into unexpected data.
Also trims the max_marker_preview_duration_desc copy to match the tone
of neighboring setting descriptions.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Follow-up to the initial ceiling-configurable change, incorporating
product-review feedback. Two design shifts plus a read-side bug fix:
- Default MaxMarkerPreviewDuration flipped from 20 to 0 (ceiling
disabled). User-set end times are now honored by default; the
ceiling becomes an opt-in safety for imports or untrusted data.
A buried setting at its old 20s default was unlikely to be found
by users hitting the silent-truncation case.
- Non-positive intervals (endSeconds <= seconds) now skip preview
generation entirely rather than falling back to the 20s default.
A user who sets zero or negative duration either made a mistake
(don't invent output) or marked a point without wanting a video
(don't generate one they didn't ask for). Either way, skip with
a warning log.
- Fix missing ConfigGeneralResult field wiring in
resolver_query_configuration.go. The schema and mutation sides
were wired in the initial commit but the query read path was
missed, causing the Settings UI to display Go's zero-value (0)
regardless of the stored config value.
Behavior change on upgrade: existing preview files remain unchanged.
To refresh previews for markers whose end times were previously
truncated at 20s, run Generate > Marker Previews with "Overwrite
Existing" enabled. To keep the old 20s ceiling, set Max marker
preview duration to 20 under Settings > System > Preview Generation.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Replaces the hardcoded maxMarkerPreviewDuration = 20 constant in
pkg/scene/generate/marker_preview.go with a configurable setting on
ConfigGeneral, mirroring the PreviewSegments wiring pattern.
- Default 20 preserves existing behavior for all installs
- Positive N sets the ceiling in seconds
- 0 (or any value <= 0) disables the ceiling, honoring explicit
endSeconds verbatim
- Adds logger.Warnf for non-positive intervals to aid diagnosis of
imported or malformed marker data
- Incidentally prevents zero/negative-duration ffmpeg calls that
were possible under the previous logic
Context: closed issue #6852 (template non-conformance), Discussion
#6851 (mobile-first direction).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* update postmigration to handle deduplicate folders.
* Split post-migration to perform some tasks before the schema migration
* Reparent files and delete duplicate folder if possible
---------
Co-authored-by: WithoutPants <53250216+WithoutPants@users.noreply.github.com>
* Add option to ignore zip file contents while cleaning
Speeds up the clean process with the assumption that files within zip files are not deleted.
* Add UI for new option
* feat: add scenes_size sort option for performers
Adds sorting performers by total file size of associated scenes.
Follows the existing scenes_duration pattern.
Ref: stashapp/stash#5530
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: add scenes_size sort option for studios
Adds sorting studios by total file size of associated scenes.
Follows the existing scenes_duration pattern.
Ref: stashapp/stash#5530
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat(ui): add Scenes Size sort option for performers and studios
Adds 'Scenes Size' to the sort dropdown for performer and studio
list views, with i18n label.
Ref: stashapp/stash#5530
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: extend scenes_size sort to tags
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Convert career start/end to date
* Update UI to accept dates for career length fields
* Fix date filtering
---------
Co-authored-by: Gykes <24581046+Gykes@users.noreply.github.com>
* feat: add image details to search filter
This change adds the image details field to the image search filter, allowing for better discovery of images based on their description.
---------
Co-authored-by: WithoutPants <53250216+WithoutPants@users.noreply.github.com>
* fix: support string-based fingerprints in hashes filter
* Fix tests and add phash test
File fingerprints weren't using correct types. Filter test wasn't using correct types. Add phash to general files.
---------
Co-authored-by: hyper440 <hyper440@users.noreply.github.com>
Co-authored-by: WithoutPants <53250216+WithoutPants@users.noreply.github.com>
* Add useDebouncedState hook
* Add basename to folder sort whitelist
* Add parent_folder criterion to gallery
* Add selection on enter if single result
* Fix stale thumbnails after file content changes
When a file's content changed (e.g. after renaming files in a gallery),
the scan handler updated fingerprints but did not bump the entity's
updated_at timestamp. Since thumbnail URLs use updated_at as a cache
buster and are served with immutable/1-year cache headers, browsers
would indefinitely serve the old cached thumbnail.
Update image, scene, and gallery scan handlers to call UpdatePartial
(which sets updated_at to now) whenever file content changes, not only
when a new file association is created.
* Skip scanning zip contents when fingerprint is unchanged
When a zip-based gallery's modification time changes but its content
hash (oshash/md5) remains the same, skip walking and rescanning every
file inside the zip. This avoids expensive per-file fingerprint
recalculation when zip metadata changes without actual content changes.
Closes#6512
* Log a debug message when skipping a zip scan due to unchanged
fingerprint
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: WithoutPants <53250216+WithoutPants@users.noreply.github.com>
* Replace panic with warning if creating a folder hierarchy where parent is equal to current
* Clean stash paths so that comparison works correctly when creating folder hierarchies
* Add basename field to folder
* Add parent_folders field to folder
* Add basename column to folder table
* Add basename filter field
* Create missing folder hierarchies during migration
* Treat files/folders in zips where path can't be made relative as not found
Addresses an issue during clean where corrupt folder entries in zip files could not be removed due to an error during the call to Rel.
* Add root paths parameter to GetOrCreateFolderHierarchy
Ensures that folders are only created up to the root library paths.
* Create full folder hierarchy when scanning a new folder
During a recursive scan, folders should be created as they are encountered (folders are handled in a single thread). This change applies only during a selective scan. Creates up to the root library folder.
* Create folder hierarchy on new file scan
This should only apply when scanning a specific file, as parent folders should be been created during a recursive scan.
* Fix existing folders with missing parents during scan
* Add reveal in file manager button to file info panel
Adds a folder icon button next to the path field in the Scene, Image,
and Gallery file info panels. Clicking it calls a new GraphQL mutation
that opens the file's enclosing directory in the system file manager
(Finder on macOS, Explorer on Windows, xdg-open on Linux).
Also fixes the existing revealInFileManager implementations which were
constructing exec.Command but never calling Run(), making them no-ops:
- darwin: add Run() to open -R
- windows: add Run() and fix flag from \select to /select,<path>
- linux: implement with xdg-open on the parent directory
- desktop.go: use os.Stat instead of FileExists so folders work too
* Disallow reveal operation if request not from loopback
---------
Co-authored-by: 1509x <1509x@users.noreply.github.com>
Co-authored-by: WithoutPants <53250216+WithoutPants@users.noreply.github.com>
