Closed ChristianDarr-personal closed 1 year ago
Merging #262 (c54c24d) into main (c5a4cd9) will increase coverage by
2.04%
. The diff coverage is13.86%
.
:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@ Coverage Diff @@
## main #262 +/- ##
========================================
+ Coverage 2.38% 4.43% +2.04%
========================================
Files 8 8
Lines 879 925 +46
========================================
+ Hits 21 41 +20
- Misses 858 883 +25
- Partials 0 1 +1
Impacted Files | Coverage Δ | |
---|---|---|
internal/driver/device.go | 11.42% <ø> (ø) |
|
internal/driver/routes.go | 0.00% <0.00%> (ø) |
|
internal/driver/driver.go | 3.48% <14.00%> (+3.48%) |
:arrow_up: |
A couple of attributions are missing in attribution.txt, that file needs to be updated.
Are these adding new dependencies that are not used else where in EdgeX? If so please see https://wiki.edgexfoundry.org/display/FA/Vetting+Process+for+3rd+Party+Dependencies
@ChristianDarr-personal , your last commit is fail Semantic PR. Amend the commit to fix spelling.
A couple of attributions are missing in attribution.txt, that file needs to be updated.
Are these adding new dependencies that are not used else where in EdgeX? If so please see https://wiki.edgexfoundry.org/display/FA/Vetting+Process+for+3rd+Party+Dependencies
These are indirect dependencies, so do we still need to do what you have suggested?
These are indirect dependencies, so do we still need to do what you have suggested?
Nope, just on the direct dependencies.
If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:
BREAKING CHANGE:
describing the break)Testing Instructions
v4l2-ctl --list-devices
to check that the device is recognized by your system and to check the paths of the device.make docker
.New Dependency Instructions (If applicable)