Skip to content
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.

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

pgsql: remove unused msg field (7.0.x backport) - v1 #10079

Closed

Conversation

jufajardini
Copy link
Contributor

The ConsolidatedDataRow struct had a length field that wasn't truly used.

Related to
Bug #6389

(cherry-picked from commit 1afb485)

Link to redmine ticket:

Describe changes:

The `ConsolidatedDataRow` struct had a `length` field that wasn't truly
used.

Related to
Bug OISF#6389

(cherry picked from commit 1afb485)
Copy link

codecov bot commented Dec 19, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (e8f3753) 82.45% compared to head (067ca94) 82.41%.

Additional details and impacted files
@@              Coverage Diff               @@
##           main-7.0.x   #10079      +/-   ##
==============================================
- Coverage       82.45%   82.41%   -0.04%     
==============================================
  Files             969      969              
  Lines          273937   273935       -2     
==============================================
- Hits           225870   225763     -107     
- Misses          48067    48172     +105     
Flag Coverage Δ
fuzzcorpus 64.22% <ø> (-0.10%) ⬇️
suricata-verify 61.08% <ø> (-0.04%) ⬇️
unittests 62.93% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

@suricata-qa
Copy link

WARNING:

field baseline test %
SURI_TLPW2_autofp_stats_chk
.uptime 188 200 106.38%

Pipeline 17155

Copy link
Member

@inashivb inashivb left a comment

Choose a reason for hiding this comment

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

This looks like a cleanup to me. I wonder why is this being backported? And, how does it relate to the linked ticket?

@jufajardini
Copy link
Contributor Author

This looks like a cleanup to me. I wonder why is this being backported? And, how does it relate to the linked ticket?

Fair. It relates to the linked ticket because the work done for the ticket will impact this field. And since it's a field that's not truly used, seemed to make sense to remove it...

@victorjulien
Copy link
Member

Merged in #10081, thanks!

@jufajardini jufajardini deleted the pgsql-unused-length-70x/v1 branch December 22, 2023 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants