movement
movement copied to clipboard
feat: add bidirectional option to filter_by_displacement
Mentioned Pr Bi-directional approach First Stage commit Not yet implemnted - edge cases, i.e. what happens if a point keeps jumping back-and-forth between two positions, in that case it's also hard to decide which position is correct. yet to be implemented as mentioned by @niksirbi.
Codecov Report
Attention: Patch coverage is 43.33333% with 17 lines in your changes missing coverage. Please review.
Project coverage is 98.92%. Comparing base (
956faf3) to head (e1d536e). Report is 4 commits behind head on main.
| Files with missing lines | Patch % | Lines |
|---|---|---|
| movement/filtering.py | 43.33% | 17 Missing :warning: |
Additional details and impacted files
@@ Coverage Diff @@
## main #531 +/- ##
===========================================
- Coverage 100.00% 98.92% -1.08%
===========================================
Files 28 28
Lines 1549 1575 +26
===========================================
+ Hits 1549 1558 +9
- Misses 0 17 +17
: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.
How did pre-commit.ci fail When I only resolved conflicts from github editor? I didn't even push new code. Do I need to push again @niksirbi?
Now the ruff commit is passing locally but when I push and resolve conflict it starts failing I am lost now
Quality Gate failed
Failed conditions
C Reliability Rating on New Code (required ≥ A)
See analysis details on SonarQube Cloud
Catch issues before they fail your Quality Gate with our IDE extension
SonarQube for IDE
Now the ruff commit is passing locally but when I push and resolve conflict it starts failing I am lost now
Make sure that the pre-commit you have locally is up-to-date with the one used in CI. In practice, this means running:
pre-commit autoupdate
pre-commit run -a
If pre-commit makes any changes, make sure to stage, commit and push them.
Understood thanks
any other changes needed? And is there a way to make the remaining 3 tests pass?
Hey @demoncoder-crypto, Just to answer your question about failing testcases
-
Sonar Cloud is failing due to unreachable code in filtering.py. ( The
raise logger.error( ValueError)on line 286 and 366 to be specific) -
Codecov is failing as there are lines in the code that have not been been tested. codecov you can find the lines that have not been tested here marked in red.
hope it helps!