-
Notifications
You must be signed in to change notification settings - Fork 26
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
[python] Allow specification of X names on ingest [release-1.6] #1996
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-1.6 #1996 +/- ##
============================================
Coverage 63.11% 63.11%
============================================
Files 106 106
Lines 10062 10062
============================================
Hits 6351 6351
Misses 3711 3711
Flags with carried forward coverage won't be shown. Click here to find out more.
|
cd apis/r | ||
wget https://github.com/TileDB-Inc/TileDB-R/archive/refs/tags/0.22.0.tar.gz | ||
Rscript -e 'remotes::install_deps("0.22.0.tar.gz")' | ||
R CMD INSTALL 0.22.0.tar.gz # as 0.22.0 is needed by SOMA 1.6 |
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.
The idea of 'controlled download' was to do just this, but via binaries. Paul and I put some work into this. But let's see if brute works.
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.
@eddelbuettel in fact this has already worked on release-1.5
.
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.
@eddelbuettel regarding controlled downgrades -- last week on #1993 despite multiple debug commits over a full day of debugging I was unable to decipher why the controlled-downgrades approach from #1994 was not working on MacOS. Since I was unable to get the pattern from #1994 applied successfully, I am now attempting to apply the successful pattern from #1972.
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 did the same in December, believe it or not, but stopped when I saw no light on either end of any tunnel.
cd apis/r | ||
wget https://github.com/TileDB-Inc/TileDB-R/archive/refs/tags/0.22.0.tar.gz | ||
Rscript -e 'remotes::install_deps("0.22.0.tar.gz")' | ||
R CMD INSTALL 0.22.0.tar.gz # as 0.22.0 is needed by SOMA 1.6 |
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.
You should not need to do it twice, you can can skip the update.packages(ask=FALSE)
too. That was from a different time fixing a different issue.
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.
@eddelbuettel I went through multiple CI iterations on #1972 on the release-1.5
branch to find, and use, a known-good pattern which we could then apply for subsequent PRs on subsequent branches.
This PR is a such a subsequent PR on a subsequent branch (release-1.6
).
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.
See the comment inline. @mojaveazure raised the same point, correctly, and may want to chime in.
It's good that it builds now -- big step forward. But we don't need to build it twice.
@@ -91,6 +87,13 @@ jobs: | |||
- name: Update Packages | |||
run: Rscript -e 'update.packages(ask=FALSE)' |
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 recommend to remove this block. It would allow you to remove the next block (ie lines 90 to 95 as well). And cut CI time down by a few minutes.
/CC @mojaveazure
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.
@eddelbuettel trying commit number 3: de92e13
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.
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.
If I look at the correct page not three for three. One, plus two cancels. We know coverage is more fragile.
https://github.com/single-cell-data/TileDB-SOMA/actions/runs/7449708671/job/20267723363
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.
@eddelbuettel I watched each one as I ran them.
- Commit 3 had three fails
- Commit 4 had a cancel (I don't know why), then a successful re-run
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.
@eddelbuettel I am happy to re-run the already-green CI another time for commit number 4.
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.
@mojaveazure CI fail with
(2.18 vs 2.19) on commit number 5: 3ce3836 I am again reverting to commits 4 and 2 (which are identical) -- this will be a commit number 6 -- 2afbd8c -- using the proven-good approach for those commits. |
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.
Dissapointing that the controlled update didn't work; it seems like our best bet is the update + reinstall
😿 Sometimes blunt tools are all we have. Also worth reiterating that AFAICT all this work 'merely' lets us get by in CI, and may do little for users of SOMA who still fight similar battles. |
@eddelbuettel indeed: as per our established procedure there are three things:
This PR addresses only the first of these three; as it is intended to do. |
I just reiterated things internally in a conversartion, it is not ideal how things are set up because it makes builds from source harder than they maybe could be. You are fighting a heroic battle with the build system, yet there are still more possible build permutations behind other curtains. It's hard and complex ... Thanks for getting this one finished! |
Issue and/or context: #1993 for the
release-1.6
branchChanges:
Notes for Reviewer: