Skip to content

Comments

Trace logs to see where CI hangs#210

Closed
Johan-Liebert1 wants to merge 1 commit intobootc-dev:mainfrom
Johan-Liebert1:ci-hang
Closed

Trace logs to see where CI hangs#210
Johan-Liebert1 wants to merge 1 commit intobootc-dev:mainfrom
Johan-Liebert1:ci-hang

Conversation

@Johan-Liebert1
Copy link
Contributor

No description provided.

Signed-off-by: Pragyan Poudyal <pragyanpoudyal41999@gmail.com>
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request aims to enable verbose logging for debugging CI hangs. However, a significant security vulnerability has been introduced: the modification to entrypoint.sh enables command tracing (set -x), which risks exposing sensitive information passed as command-line arguments in logs. Furthermore, these debugging changes are not suitable for permanent integration due to excessive logging and potential performance degradation. Please address the security vulnerability and revert all debugging changes before merging.

@@ -1,5 +1,5 @@
#!/bin/bash
set -euo pipefail
set -xeuo pipefail

Choose a reason for hiding this comment

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

security-medium medium

The set -x option introduces a critical security vulnerability by printing all executed commands and their arguments, including sensitive information like passwords or API tokens, to standard error. This poses a significant risk in CI/CD environments where logs are persisted. Furthermore, set -x is overly verbose and not intended for permanent inclusion in production code.

Suggested change
set -xeuo pipefail
set -euo pipefail

let stdout = cmd!(
sh,
"{bck} ephemeral run --rm --label {label} --itype u1.micro --execute {script} {image}"
"{bck} ephemeral run --rm --label {label} --env RUST_LOG=trace --itype u1.micro --execute {script} {image}"

Choose a reason for hiding this comment

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

medium

Enabling trace-level logging via RUST_LOG=trace is useful for debugging, but it will generate a large amount of log output. This should be removed before merging to avoid excessive noise in test logs.

Suggested change
"{bck} ephemeral run --rm --label {label} --env RUST_LOG=trace --itype u1.micro --execute {script} {image}"
{bck} ephemeral run --rm --label {label} --itype u1.micro --execute {script} {image}

@Johan-Liebert1
Copy link
Contributor Author

It passed? I guess #209 just needs a restart?

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.

1 participant