Skip to content

chore(internal_events): remove blanket dead_code allows from remaining internal events - #26806

Merged
JinchengCao merged 4 commits into
masterfrom
JinchengCao-misc-internal-events-dead-code
Oct 23, 2026
Merged

JinchengCao merged 4 commits into
masterfrom
JinchengCao-misc-internal-events-dead-code

Conversation

@JinchengCao

@JinchengCao JinchengCao commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

Summary

Remove the module-wide allow(dead_code) from the remaining internal events modules (aws_sqs, http_client_source, parser, prometheus, unix) by gating each event on the features that use it. Event implementations are unchanged. In parser.rs, the unused RETAIN_EVENT constant is removed, and the redundant allow(dead_code) on DROP_EVENT is dropped since every feature that compiles the module uses it.

Events Used by Now gated on
SqsMessageReceiveSucceeded, SqsMessageProcessingSucceeded, SqsS3EventRecordInvalidEventIgnored aws_s3 source existing mod s3: sources-aws_s3
HttpClientEventsReceived sources::util::http_client and sources::okta::client item-level: sources-http_client, sources-prometheus_scrape or sources-okta (same gate as sources::util::http_client)
ParserMatchError, ParserConversionError, truncate_string_at kubernetes_logs source mod kubernetes_logs: sources-kubernetes_logs
PrometheusRemoteWriteParseError prometheus_remote_write source item-level: sources-prometheus_remote_write
UnixSocketFileDeleteError unix socket sources item-level: sources-utils-net-unix, sources-socket or sources-dnstap

References

Related: #23659

Vector configuration

NA

How did you test this PR?

  • Clippy and cargo hack check --each-feature pass with no warnings for each feature that compiles these modules, and with no features.
  • Related unit tests and make check-fmt pass.

Does this PR include user facing changes?

  • Yes.
  • No.

@JinchengCao JinchengCao added the no-changelog Changes in this PR do not need user-facing explanations in the release changelog label Oct 22, 2026
@JinchengCao
JinchengCao marked this pull request as ready for review October 23, 2026 16:34
@JinchengCao
JinchengCao requested a review from a team as a code owner October 23, 2026 16:34
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-23T17:48:50.750408Z b6f8fa5 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@datadoghq-integration datadoghq-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bits Code Review: PASS

More details

The static reviewer found the feature gates consistent with existing callers and Cargo dependencies, with no actionable regressions. No human PR discussion added concerns or qualifications.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit e7b8f20

@JinchengCao
JinchengCao enabled auto-merge October 23, 2026 17:56
@JinchengCao
JinchengCao added this pull request to the merge queue Oct 23, 2026
Merged via the queue into master with commit 9f80eb2 Oct 23, 2026
86 checks passed
@JinchengCao
JinchengCao deleted the JinchengCao-misc-internal-events-dead-code branch October 23, 2026 18:53
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 23, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

no-changelog Changes in this PR do not need user-facing explanations in the release changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants