Skip to content

websocket: accepts config value with units - #15633

Closed
catenacyber wants to merge 1 commit into
OISF:mainfrom
catenacyber:websocket-conf-kib-8552-v2
Closed

websocket: accepts config value with units#15633
catenacyber wants to merge 1 commit into
OISF:mainfrom
catenacyber:websocket-conf-kib-8552-v2

Conversation

@catenacyber

Copy link
Copy Markdown
Contributor

Link to ticket: https://redmine.openinfosecfoundation.org/issues/8552

Describe changes:

  • websocket: accepts config value with units

#15627 with rustfmt fix

Ticket: 8552

As was the commented out example
@suricata-qa

Copy link
Copy Markdown

Information: QA ran without warnings.

Pipeline = 32018

@codecov

codecov Bot commented Jun 12, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.87%. Comparing base (8a4eea4) to head (dd0cd2b).

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15633      +/-   ##
==========================================
- Coverage   82.87%   82.87%   -0.01%     
==========================================
  Files        1006     1006              
  Lines      273527   273530       +3     
==========================================
- Hits       226698   226695       -3     
- Misses      46829    46835       +6     
Flag Coverage Δ
fuzzcorpus 61.36% <0.00%> (-0.01%) ⬇️
livemode 18.40% <0.00%> (-0.01%) ⬇️
netns 22.81% <0.00%> (+0.03%) ⬆️
pcap 45.16% <0.00%> (-0.06%) ⬇️
suricata-verify 66.65% <0.00%> (-0.02%) ⬇️
unittests 58.52% <0.00%> (-0.01%) ⬇️

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

if let Ok(vu) = u32::try_from(v) {
WEBSOCKET_MAX_PAYLOAD_SIZE = vu;
} else {
SCLogError!(

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I wish we would fix this pattern. We issue errors, but they have no effect, so they are effectively warnings. But we really should propagate these errors I think. Anyway, since this is a common pattern I'll not block the PR over it.

@victorjulien victorjulien added this to the 9.0 milestone Jun 12, 2026
@victorjulien

Copy link
Copy Markdown
Member

Merged in #15636, thanks!

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.

3 participants