Skip to content

Remove invalid distinct key from postfix very-slow user-enum scenario#1811

Draft
Copilot wants to merge 1 commit into
masterfrom
copilot/fix-review-comment-3310676293
Draft

Remove invalid distinct key from postfix very-slow user-enum scenario#1811
Copilot wants to merge 1 commit into
masterfrom
copilot/fix-review-comment-3310676293

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 27, 2026

Description

The review feedback flagged distinct: evt.Meta.sasl_username as non-functional for this scenario. This update applies the requested change exactly by removing distinct from the melite/postfix-very-slow-bf_user-enum definition.

  • Scope
    • Updated only scenarios/melite/postfix-very-slow-bf.yaml.
  • Change
    • Removed distinct: evt.Meta.sasl_username from the user-enum variant.
  • Before/After
    # before
    groupby: evt.Meta.source_ip
    distinct: evt.Meta.sasl_username
    leakspeed: "4h"
    
    # after
    groupby: evt.Meta.source_ip
    leakspeed: "4h"

Checklist

  • I have read the contributing guide
  • I have tested my changes locally
  • For new parsers or scenarios, tests have been added
  • I have run the hub linter and no issues were reported (see contributing guide)
  • Automated tests are passing
  • AI was used to generate any/all content of this PR

Copilot AI changed the title [WIP] Fix code by removing distinct as suggested in review Remove invalid distinct key from postfix very-slow user-enum scenario May 27, 2026
Copilot finished work on behalf of sabban May 27, 2026 14:21
Copilot AI requested a review from sabban May 27, 2026 14:21
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.

2 participants