Repository navigation
fix(OSQUERY-008): CU-86akhf8u2 File-scope constant kMaxEventLatency violates established kPascalCase-only scoping/anonymous-namespace convention - #103
Draft
flamingo[bot] wants to merge 1 commit into
Conversation
…lished kPascalCase-only scoping/anonymous-namespace convention
| DECLARE_bool(enable_file_events); | ||
|
|
||
| namespace { | ||
| const int kMaxEventLatency = 3000; |
Author
There was a problem hiding this comment.
🦩 🟠 File-scope constant kMaxEventLatency violates established kPascalCase-only scoping/anonymous-namespace convention
Wrapped const int kMaxEventLatency = 3000; in an anonymous namespace (namespace { ... } // namespace) directly where it was declared inside namespace osquery, giving it internal linkage per translation unit and satisfying OSQUERY-007 scoping convention while preserving its use in all subsequent TEST_F bodies unchanged.
🤖 Prompt for AI agents
In osquery/events/tests/linux/inotify_tests.cpp around line 32, review and complete this code-review fix: File-scope constant kMaxEventLatency violates established kPascalCase-only scoping/anonymous-namespace convention.
What the draft fix changed: Wrapped `const int kMaxEventLatency = 3000;` in an anonymous namespace (`namespace { ... } // namespace`) directly where it was declared inside `namespace osquery`, giving it internal linkage per translation unit and satisfying OSQUERY-007 scoping convention while preserving its use in all subsequent `TEST_F` bodies unchanged.
Verify the change is correct and complete; do not refactor unrelated code.
fix confidence: 🟢 95 high — react 👍/👎 to teach the reviewer
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes findings from rule OSQUERY-008 — File-scope constant kMaxEventLatency violates established kPascalCase-only scoping/anonymous-namespace convention.
Draft — this is a starting point, not a finished change. The fix required judgment, so read it before trusting it.
osquery/events/tests/linux/inotify_tests.cpp:32What changed — and what was deliberately left — is explained per finding as inline review comments on the lines each finding touched.
Run: https://product-hub.flamingo.so/admin/code-review
Run id:
46e37628-c6c9-49a4-aa29-9b30b2c8be3fMerging this PR is recorded as acceptance of the rule that produced it;
closing it unmerged is recorded as rejection. Both feed rule health, so
closing a wrong suggestion is useful rather than merely tidy.
ClickUp task: CU-86akhf8u2 Osquery review findings sweep (15 PRs)