-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: How does wait-images work? #56
Comments
You should give the names of all of the images on the command line, even if the files do not exist yet. The program will then wait for the the files to appear. |
Thank you for the response. You sure about that? 😄 |
There are some internal temporary file names that are not saved unless |
Hmm ok. For testing I set --wait-images=50.0 and add 50 images-paths as files. And start the application after the first image is saved to a file. My expected behavior is, that the application (no matter what "waiting" exactly means) runs more or less 50s, if not all images are going to be created. My thought is: |
Can you attach a verbose log and the command line used?
|
Thank you! I found a problem on my side within the pipeline 👍 It runs now, but if not all images are available it exits with "Error exit due to failed steps". Do all images have to be created? |
Hi,
I tried to use --wait-images=5.0 for testing, but the application closes after merging the two initial images, regardless if I add images to the folder after a second or not. Do I have to use a specific directory? What am I doing wrong here?
The text was updated successfully, but these errors were encountered: