-
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
cleanup(sinsp): handle path too long in a better way #2160
Conversation
Signed-off-by: Andrea Terzolo <andreaterzolo3@gmail.com>
not sure if 0.19.0 or 0.20.0, it should be quite safe |
Perf diff from master - unit tests
Heap diff from master - unit tests
Heap diff from master - scap file
Benchmarks diff from master
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2160 +/- ##
=======================================
Coverage 74.77% 74.77%
=======================================
Files 254 254
Lines 33505 33511 +6
Branches 5748 5748
=======================================
+ Hits 25053 25058 +5
- Misses 8452 8453 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
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 |
LGTM label has been added. Git tree hash: f7bbdc97c9cd5ce6fe6c6e822a3ddde031fa5f41
|
What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area libsinsp
Does this PR require a change in the driver versions?
No
What this PR does / why we need it:
Today in case of path is too long we return
/PATH_TOO_LONG
. This means:fd_directory
= "/"fd_filename
= "PATH_TOO_LONG"The directory is definitely wrong and misleading as a workaround I propose something like this
/DIR_TOO_LONG/FILENAME_TOO_LONG
, so:fd_directory
= "/DIR_TOO_LONG"fd_filename
= "FILENAME_TOO_LONG"We probably need to find something better but at least we remove the wrong dir
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: