-
Notifications
You must be signed in to change notification settings - Fork 169
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
fix(userspace/libsinsp): do not immediately process async events whose timestamp is in the future in case a SCAP_TIMEOUT is received #2250
base: master
Are you sure you want to change the base?
Conversation
…e timestamp is in the future in case a SCAP_TIMEOUT is received. Instead, they'll be processed at the future time, as requested by the async event generator. Signed-off-by: Federico Di Pierro <[email protected]>
/milestone 0.21.0 |
Perf diff from master - unit tests
Heap diff from master - unit tests
Heap diff from master - scap file
Benchmarks diff from master
|
/cc @jasondellaluce |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2250 +/- ##
==========================================
- Coverage 75.16% 75.16% -0.01%
==========================================
Files 278 278
Lines 34478 34479 +1
Branches 5922 5924 +2
==========================================
Hits 25916 25916
- Misses 8562 8563 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Andreagit97, FedeDP The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold for a review by Jason |
/unhold |
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area libsinsp
Does this PR require a change in the driver versions?
What this PR does / why we need it:
Right now, when a SCAP_TIMEOUT is received from the scap_engine, if the async queue contains any event, it gets popped and processed without further investigation about the event's timestamp.
With the proposed patch, the async queue gets scanned considering
now
as timestamp; this way, we honor the requested timestamp by the async event generator: if it is in the future, we hold the event until that time in the future has arrived.This PR was originally made as part of the work for #2207, but since it could be extracted, here i am :)
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: