Skip to content

timeout parameter related changes re IDETECT-5074#1715

Merged
cpottsbd merged 7 commits into11.4.zfrom
cp_IDETECT-5074
Apr 15, 2026
Merged

timeout parameter related changes re IDETECT-5074#1715
cpottsbd merged 7 commits into11.4.zfrom
cp_IDETECT-5074

Conversation

@cpottsbd
Copy link
Copy Markdown
Contributor

@cpottsbd cpottsbd commented Apr 7, 2026

Timeout parameter related changes re IDETECT-5074
Update detect.timeout parameter to appear in Basic + All Properties pages
Add troubleshooting note.

cpottsbd added 3 commits April 7, 2026 10:21
remove this change imported from another PR (Will get covered under that PR)

## Exceeding configured timeouts

- When `--detect.waiting.for.results` or `--detect.timeout CLI arguments` parameters are specified for [detect_product_short] the variable nature of scan completion times may cause [detect_product_short] to indicate a timeout. Scan completion time is influenced by the size of the scanned code base and the extent of conncurrent load on [bd_product_short]. Should no other [detect_product_short] scan exceptions be indicated, [detect_product_short] timeout may not indicate a scan failure. Users can continue to monitor the scan within [bd_product_short] itself after [detect_product_short] stops waiting for results.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Believe this should be detect.wait.for.results

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

100% Thank you.


## Exceeding configured timeouts

- When `--detect.wait.for.results` or `--detect.timeout CLI arguments` parameters are specified for [detect_product_short] the variable nature of scan completion times may cause [detect_product_short] to indicate a timeout. Scan completion time is influenced by the size of the scanned code base and the extent of concurrent load on [bd_product_short]. Should no other [detect_product_short] scan exceptions be indicated, [detect_product_short] timeout may not indicate a scan failure. Users can continue to monitor the scan within [bd_product_short] itself after [detect_product_short] stops waiting for results.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"When --detect.wait.for.results or --detect.timeout CLI arguments parameters are specified for Detect the variable nature of scan completion times may cause Detect to indicate a timeout."

Nit but do we want a command after the first "Detect"?

@cpottsbd cpottsbd merged commit 8eababb into 11.4.z Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants