darktable-cli: problems with export, if composit with the same image

LowerFrank commented 2 months ago

Describe the bug

If you perform the composite with the same image, the export with darktable-cli

(<darktable-cli /.../.../.../.../[imagename.orf] /.../.../.../.../[imagename.jpeg] --core --conf plugins/imageio/format/jpeg/quality=100 --conf plugins/imageio/storage/disk/overwrite=1>)

the error occurs <3.9861 [image_cache_allocate] failed to open image 36031 from database: no more rows available>

The error does not occur if a different physical image is used in the composite.
The error does not occur if the export is made directly from the darktable interface

I was able to reproduce the problem with

different image types (orf, jpg, ...)
in different DT databases
on different PCs (Linux Mint 21.1 Vera, Linux Mint 21.1 Victoria, Windows 10)
each in DT version 4.8.0

Steps to reproduce

open a photo in the darkroom
select effects and then composite
drag the same image from the filmstrip into the composite
exit DT
perform an export comparable to this <darktable-cli /.../.../.../.../[imagename.orf] /.../.../.../.../[imagename.jpeg] --core --conf plugins/imageio/format/jpeg/quality=100 --conf plugins/imageio/storage/disk/overwrite=1>

Expected behavior

the cli-export should work like the export in the program

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

4.8.0

What OS are you using?

Linux

What is the version of your OS?

Mint 21.1 Vera

Describe your system?

No response

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

github-actions[bot] commented 3 weeks ago

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

LowerFrank commented 3 weeks ago

Tested with DT 4.8.1. The error still occurs.

darktable-org / darktable