Skip to content
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

Send bbox again #173

Merged
merged 2 commits into from
Oct 26, 2023
Merged

Send bbox again #173

merged 2 commits into from
Oct 26, 2023

Conversation

MateoLostanlen
Copy link
Member

We can send bboxes again with pr #267 merge so let's do it :)

Small change too, there was an unnecessary string conversion

@codecov
Copy link

codecov bot commented Oct 26, 2023

Codecov Report

Merging #173 (5d8a846) into develop (49a23fb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #173   +/-   ##
========================================
  Coverage    87.80%   87.80%           
========================================
  Files            6        6           
  Lines          369      369           
========================================
  Hits           324      324           
  Misses          45       45           
Flag Coverage Δ
unittests 87.80% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
pyroengine/engine.py 89.62% <ø> (ø)

@MateoLostanlen MateoLostanlen requested review from a team October 26, 2023 20:59
@MateoLostanlen MateoLostanlen self-assigned this Oct 26, 2023
@MateoLostanlen MateoLostanlen merged commit f01f2f3 into develop Oct 26, 2023
14 of 15 checks passed
@MateoLostanlen MateoLostanlen deleted the send_bbox_again branch October 26, 2023 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant