Skip to content

Cherry-pick #285, #280 to main #327

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

Merged
merged 3 commits into from
Jan 10, 2022
Merged

Conversation

scpeters
Copy link
Member

@scpeters scpeters commented Dec 22, 2021

I believe #280 and #285 will help resolve some issues in #283.

Remember to use rebase-and-merge

@scpeters scpeters requested a review from ahcorde December 22, 2021 07:50
@codecov
Copy link

codecov bot commented Dec 22, 2021

Codecov Report

Merging #327 (60b8964) into main (6a80aa4) will increase coverage by 0.23%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #327      +/-   ##
==========================================
+ Coverage   99.30%   99.53%   +0.23%     
==========================================
  Files          68       68              
  Lines        6290     6275      -15     
==========================================
  Hits         6246     6246              
+ Misses         44       29      -15     
Impacted Files Coverage Δ
include/ignition/math/Vector2.hh 100.00% <100.00%> (ø)
include/ignition/math/Vector3.hh 100.00% <100.00%> (+1.15%) ⬆️
include/ignition/math/Vector4.hh 100.00% <100.00%> (+4.61%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6a80aa4...60b8964. Read the comment docs.

@chapulina
Copy link
Contributor

Cherry-picking will make the commits still show up when we see the branch comparison. Can we do it as a merge forward like previous PRs?

@scpeters
Copy link
Member Author

Cherry-picking will make the commits still show up when we see the branch comparison. Can we do it as a merge forward like previous PRs?

the idea was to help expedite a fix for the test failures in #283, but if there's not a rush, then I'll just continue merging forward incrementally

@scpeters scpeters closed this Dec 27, 2021
@scpeters scpeters reopened this Jan 10, 2022
ahcorde and others added 2 commits January 10, 2022 11:39
Signed-off-by: ahcorde <ahcorde@gmail.com>
Ccreated wrappers for Vector2, 3 and 4 with pybind11

Signed-off-by: ahcorde <ahcorde@gmail.com>

Co-authored-by: Steve Peters <scpeters@openrobotics.org>
Signed-off-by: Steve Peters <scpeters@openrobotics.org>
@scpeters scpeters merged commit 3cc9adb into gazebosim:main Jan 10, 2022
@scpeters scpeters deleted the pick_pybind11_main branch January 10, 2022 23:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants