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

detect/flow: move keyword parsing code to rust #12606

Closed

Conversation

catenacyber
Copy link
Contributor

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

Describe changes:

  • detect/flow: move keyword parsing code to rust

#12604 with warning/cast fix

for flow.pkts and flow.bytes keywords

Ticket: 7562

Avoid null deref when parsing flow.bytes:toserver;
Copy link

codecov bot commented Feb 17, 2025

Codecov Report

Attention: Patch coverage is 96.58120% with 4 lines in your changes missing coverage. Please review.

Project coverage is 80.75%. Comparing base (10ede91) to head (a4f2171).
Report is 19 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #12606      +/-   ##
==========================================
+ Coverage   80.74%   80.75%   +0.01%     
==========================================
  Files         931      932       +1     
  Lines      259144   259139       -5     
==========================================
+ Hits       209242   209270      +28     
+ Misses      49902    49869      -33     
Flag Coverage Δ
fuzzcorpus 56.98% <46.15%> (+0.01%) ⬆️
livemode 19.39% <0.00%> (+<0.01%) ⬆️
pcap 44.15% <0.00%> (-0.01%) ⬇️
suricata-verify 63.46% <95.04%> (+0.02%) ⬆️
unittests 58.36% <32.47%> (+0.01%) ⬆️

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

@suricata-qa
Copy link

Information: QA ran without warnings.

Pipeline 24760

@victorjulien victorjulien added this to the 8.0 milestone Feb 18, 2025
@victorjulien
Copy link
Member

Merged in #12625, 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