Skip to content
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

After a script task has finished, the process is updated slowly #3671

Closed
matthias-ronge opened this issue May 20, 2020 · 6 comments
Closed
Labels

Comments

@matthias-ronge
Copy link
Collaborator

Extracted from comment on issue #3279 by @mnscholz:

Although the script finishes instantly (< 1s), the process is updated/advanced in Kitodo only after a very long time (10-30min). Why is there so much idle time?

@solth
Copy link
Member

solth commented May 25, 2020

Could this perhaps be related to and fixed by #3687 ?

@matthias-ronge
Copy link
Collaborator Author

Needs to check whether that is currently still the case.

@matthias-ronge matthias-ronge self-assigned this Nov 3, 2020
@matthias-ronge matthias-ronge removed their assignment Jan 26, 2021
@andre-hohmann
Copy link
Collaborator

@matthias-ronge: Does the problem still persists?

"Our" automatic tasks (Image validation, generation of Images, ...) are processed quickly and also the status of the process is quickly updated.

@matthias-ronge
Copy link
Collaborator Author

I don't know at the moment. There are no shell scripts in the Production 3 systems that I maintain. The problem here was with external shell scripts in automatic tasks, not with internal functions like generation of images.

@m-kotzyba, you use a lot of scripts in your workflow, what have you observed in this regard?

@m-kotzyba
Copy link
Collaborator

Currently we run just a “MD5 Check” and a “Remove all images from thumbs, max and in the meta.xml” (in case of faulty scans) as external shell scrip but these scripts are not automated but manually triggered.

However, while the (productive) work with Kitodo and also (all) my tests, I did not experienced the described delay of 10-30 min. in the process status update (yet).

@matthias-ronge
Copy link
Collaborator Author

So I assume #3687 did fix this. I will close the ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants