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

Error in separating document into pages , timeout 120s #306

Closed
Bate5-m4wy opened this issue Jan 11, 2023 · 3 comments · Fixed by #332
Closed

Error in separating document into pages , timeout 120s #306

Bate5-m4wy opened this issue Jan 11, 2023 · 3 comments · Fixed by #332
Assignees
Labels
stretch goal timeout Dangerzone Times Out
Milestone

Comments

@Bate5-m4wy
Copy link

I am new to coding and stuff so i dont know how can i increase the timeout delay of 'danger-zone' process as i saw another thread discussing this issue saying that a 1000 page pdf would need about 500 seconds or smth like that , so kindly can someone help me with it?
btw os: Win11

@apyrgio
Copy link
Contributor

apyrgio commented Jan 12, 2023

Right, the timeout problem has not been adequately addressed yet. Unfortunately, there is no CLI option that we can provide you to tweak it, so for now, you'd have to go in dev mode to change it. If you're up for it, I can guide you:

  1. Download Dangerzone with Git for Windows.

  2. Edit dangerzone/container/dangerzone.py with your editor, and bump this timeout to something higher:

    DEFAULT_TIMEOUT: float = 120

  3. Follow our build instructions for Windows and use .\dev_scripts\dangerzone.bat to run the edited Dangerzone app locally.

Alternatively, you'd have to wait for the 0.4.1 release, where we address this problem. It's expected to be out in early February.

@apyrgio
Copy link
Contributor

apyrgio commented Jan 12, 2023

A bit more context for others that may encounter this problem:

What is the underlying problem?

We are making a conversion from a single PDF to a PDF per page using a constant timeout for the whole process (120s). The reason we do so is because we don't know the number of pages at that point (see also #70).

How can we fix this problem?

We have a PR that replaces pdftk in favor of pdftoppm, and will add a timeout that is proportional to the number of pages (see #305).

@Bate5-m4wy
Copy link
Author

sorry for late replying , got busy
thank you so much i will try and tell u the result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stretch goal timeout Dangerzone Times Out
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants