bpftime
bpftime copied to clipboard
eunomia-bpf
fix: do not shift in map_by_fd
Description
The old version shift 32 bit in map_by_fd, we don't need to do that.
Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
Project coverage is 55.42%. Comparing base (
9e35e28) to head (872ff64).
| Files with missing lines | Patch % | Lines |
|---|---|---|
| runtime/src/bpftime_shm.cpp | 0.00% | 2 Missing :warning: |
| runtime/src/bpf_map/userspace/map_in_maps.hpp | 0.00% | 1 Missing :warning: |
Additional details and impacted files
@@ Coverage Diff @@
## master #344 +/- ##
==========================================
- Coverage 58.01% 55.42% -2.59%
==========================================
Files 105 90 -15
Lines 7777 6538 -1239
Branches 839 544 -295
==========================================
- Hits 4512 3624 -888
+ Misses 3265 2914 -351
Flags with carried forward coverage won't be shown. Click here to find out more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
![codecov[bot] avatar](https://avatars.githubusercontent.com/in/254?v=4 "Published by a pub.dev verified publisher"){kind=small}
⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.
Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.
🔎 Detected hardcoded secret in your pull request
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 8730391 | Triggered | Generic Private Key | 872ff64aca2357e294aca4a2141493e714e3ce63 | benchmark/deepflow/go-server/key.pem | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
![gitguardian[bot] avatar](https://avatars.githubusercontent.com/in/46505?v=4 "Published by a pub.dev verified publisher"){kind=small}