darktable-org / darktable-org/lua-scripts
Tempfiles exported for use by a lua script (e.g. `hugin`) disappear immediately after export
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 219
- Forks
- 142
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce:
- enable
contrib/huginscript, and ensure paths are configured correctly and hugin is installed - select images you want to stitch into a panorama
- in export dialog, select "hugin panorama" as "target storage"
- select file format (e.g. TIFF)
- (optionally, makes no difference) tick "launch hugin gui"
- run
inotifywait -m /tmp -e create --format '%w%f' | while read f; echo "$f"; end(or similar) in terminal - press "start export"
- wait for export to finish, see toast message "launching hugin"
- nothing happens
- check inotify and see that all images were created at one point (i.e. one log line per image in the form of
/tmp/DSCF0721.tif) - check dartable log and see:
sh: line 1: '/path/to/hugin' '/tmp/DSCF0720.tif' '/tmp/DSCF0713.tif' '/tmp/DSCF0721.tif' '/tmp/DSCF0715.tif' '/tmp/DSCF0718.tif' '/tmp/DSCF0717.tif' '/tmp/DSCF0716.tif' '/tmp/DSCF0714.tif' '/tmp/DSCF0719.tif' : No such file or directory - note:
/path/to/huginDOES exist and is the hugin executable ls /tmpshows images are gone
I assume they somehow get cleaned from /tmp after the darktable export process (?) exits and the files are essentially orphaned.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the contrib/hugin script and reproduce the export while watching /tmp and the darktable log. Trace when the exported images are cleaned up relative to the hugin launch; done means the generated images remain available when hugin is invoked and the reported export workflow opens successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100