Skip to content

[For Test Only]: add debug log in idle extension loop #1180

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.

Sign up for GitHub

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

Closed
litianningdatadog wants to merge 1 commit into from
+1 −0
Closed

[For Test Only]: add debug log in idle extension loop #1180

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions bottlecap/src/bin/bottlecap/main.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -282,6 +282,7 @@ async fn extension_loop_idle(
match extension::next_event(client, &r.extension_id, &aws_config.runtime_api).await {
Ok(_) => {
debug!("Extension is idle, skipping next event");
debug!("This is a test");
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot Apr 10, 2026

Choose a reason for hiding this comment

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

P3 Badge Remove leftover test log from idle loop

This adds a non-actionable "This is a test" message inside extension_loop_idle, which executes continuously while the extension is idle. In debug-enabled environments, this will generate repetitive noise on every idle event and make it harder to diagnose real issues from logs; it appears to be test-only output rather than production telemetry.

Useful? React with 👍 / 👎.

}
Err(e) => {
error!("Error getting next event: {e:?}");
Expand Down
Loading