-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix: implemented temporary workaround suggested by TileDB. (#2251) #58
Conversation
Codecov Report
@@ Coverage Diff @@
## main #58 +/- ##
==========================================
+ Coverage 70.04% 70.05% +0.01%
==========================================
Files 138 138
Lines 10922 10926 +4
==========================================
+ Hits 7650 7654 +4
Misses 3272 3272
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
server/compute/diffexp_cxg.py
Outdated
futures.append( | ||
executor.submit( | ||
_mean_var_sparse_ab, | ||
adaptor.open_array("X"), row_selector_A, nA, row_selector_B, nB, cols)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
adaptor.open_array("X")
is the actual workaround the rest is reformatting to placate flake8.
server/compute/diffexp_cxg.py
Outdated
executor.submit(_mean_var_ab, matrix, row_selector_AB, row_selector_A_in_AB, row_selector_B_in_AB, cols) | ||
executor.submit( | ||
_mean_var_ab, | ||
adaptor.open_array("X"), row_selector_AB, row_selector_A_in_AB, row_selector_B_in_AB, cols) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
adaptor.open_array("X")
is the actual workaround the rest is reformatting to placate flake8.
Note, as discussed at the war room meeting, holding off on merging this workaround until 15:00 PT today til we hear back from TileDB regarding an ETA for a fix. |
@@ -19,6 +19,6 @@ pandas>=1.0,!=1.1 # pandas 1.1 breaks tests, https://github.com/pandas-dev/pand | |||
PyYAML>=5.4 # CVE-2020-14343 | |||
scipy>=1.4 | |||
requests>=2.22.0 | |||
tiledb>=0.9 | |||
tiledb==0.10.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pinned at 0.10.0 (current version) instead of specifying >=0.10.0
since, under the covers in TileDB-Py, the embedded TileDB versions can also get incremented.
This seems safer to me, but if I'm wrong, please let me know!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this seems fine to me. I'm unclear why all versions are not pinned. For our internal repo (ie, single-cell-explorer), we have no need to support multiple versions, and can safely pin.
This is not true for the cellxgene repo, which needs to allow users some flexibility.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was wondering about that too. 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, based solely on visual inspection.
Reviewers
Functional:
@bkmartinjr, @MDunitz
Readability:
@ebezzi
Changes
Reviewer Notes
X
andX_col_shift
arrays.