This repository has been archived by the owner on Jan 2, 2023. It is now read-only.
Update createRequest warning message to indicate a possible solution #5101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change updates the
createRequest
signal on adisposed
NetworkAccessManager
warning message to indicate one more issue that may be fixed by a user controlled setting. This was discovered by running with--log-level debug
which I added in b8f9f5e / #4668 and seeing the debug message "Loading done; Stopping QWebPage and any possible page refreshes." before I expected it to be called (before an API request hadfinished). This is called by the
loadFinished
handlerwkhtmltopdf/src/lib/multipageloader.cc
Lines 336 to 340 in 5b26acc
loadDone
was being called too early. I don't believe the immediateloadDone()
is being called because the default JavaScript delay is 200ms, but setting the timeout to a larger value fixed the issue for me, and logging this suggestion as a warning may help someone else when debugging.