-
Notifications
You must be signed in to change notification settings - Fork 165
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
wip: chore(userspace/libsinsp): move user group manager on container_id changed refresh to a RAII object #2194
base: master
Are you sure you want to change the base?
Conversation
…anged refresh to a RAII object. Also, avoid subscribing to container manager "container removed" callback; instead, use same RAII object to check whether init pid for the container did exit. Signed-off-by: Federico Di Pierro <[email protected]>
/milestone 0.20.0 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
Perf diff from master - unit tests
Heap diff from master - unit tests
Heap diff from master - scap file
Benchmarks diff from master
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2194 +/- ##
==========================================
+ Coverage 75.20% 75.21% +0.01%
==========================================
Files 259 259
Lines 33890 33902 +12
Branches 5801 5801
==========================================
+ Hits 25487 25500 +13
+ Misses 8403 8402 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area libsinsp
What this PR does / why we need it:
If a way similar to #2182, move logic to refresh user/group info upon container_id changes to a RAII object instantiated by
sinsp::next()
.This allows to take into consideration eventual "container_id" changes made by plugin parsers.
While right now there is no need for this, it will be mandatory for the container plugin, since it will be responsible to actually write the
container_id
state entry for threadinfo.Also, avoid relying upon container manager
on_remove_container
callback; instead check if aprocexit
event was received on container's init pid.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: