-
Notifications
You must be signed in to change notification settings - Fork 172
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
export.vulns default timeout /give up #715
Comments
Yes, when using the It's worth considering that making the timeout field un-ignorable might not be a good idea in some cases. There are situations where exports might take longer than usual (but completes regardless) due to various factors. In such scenarios, enforcing a strict timeout could lead to premature termination of the pyTenable process, preventing the user from downloading the contents of the export when it becomes available. |
Describe the bug
export.vulns does not seem to have a reasonable timeout. Please note the timestamps between the first logging statements from pyTenable. I called
all_vulns = list(tio.exports.vulns(last_found=cut_off,severity=["low","medium","high","critical"]))
at2023-07-21 21:34:32,301.301
. It took a couple days for the export vulns code to finally give up and for the script to exit uncleanly, alerting me that a restart is required. I assume this was caused by a Tenable outage over the weekend.If i understand the docs correctly, a timeout passed when calling the export vulns method would be ignored once the export starts?
logs from pyTenable
To Reproduce
Steps to reproduce the behavior:
I can't provide steps, I believe a Tenable outage is required to reproduce.
Expected behavior
I would expect the export vulns method to timeout or raise an error sooner.
The text was updated successfully, but these errors were encountered: