Skip to content

BUG: Fix no_lock not work #72

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
Sep 4, 2023
Merged

Conversation

codingl2k1
Copy link
Contributor

What do these changes do?

Related issue number

Fixes #xxxx

Check code requirements

  • tests added / passed (if needed)
  • Ensure all linting tests pass

@XprobeBot XprobeBot added this to the v0.1.1 milestone Sep 1, 2023
@codingl2k1 codingl2k1 changed the title Fix no_lock not work BUG: Fix no_lock not work Sep 1, 2023
@XprobeBot XprobeBot added the bug Something isn't working label Sep 1, 2023
@codecov
Copy link

codecov bot commented Sep 1, 2023

Codecov Report

Merging #72 (d2d4e7b) into main (5838440) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #72   +/-   ##
=======================================
  Coverage   88.82%   88.82%           
=======================================
  Files          47       47           
  Lines        3928     3928           
  Branches      757      757           
=======================================
  Hits         3489     3489           
- Misses        352      353    +1     
+ Partials       87       86    -1     
Flag Coverage Δ
unittests 88.64% <ø> (ø)

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

see 1 file with indirect coverage changes

@codingl2k1 codingl2k1 marked this pull request as ready for review September 1, 2023 06:21
@ChengjieLi28 ChengjieLi28 merged commit 7ae4731 into xorbitsai:main Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants