-
Notifications
You must be signed in to change notification settings - Fork 79
Individual parents merge #1125
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
Individual parents merge #1125
Conversation
|
Nice one on getting this rebased, hope it wasn't too much trouble! I'll have a detailed look tomorrow. |
Codecov Report
@@ Coverage Diff @@
## main #1125 +/- ##
==========================================
- Coverage 93.71% 93.65% -0.07%
==========================================
Files 26 26
Lines 21082 21236 +154
Branches 900 900
==========================================
+ Hits 19757 19888 +131
- Misses 1288 1311 +23
Partials 37 37
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
|
The final rebase was pretty simple - the patching process took care of everything. But it looks like the same test coverage check is failing this time. There is also an outstanding issue of documenting these changes. Does this need to happen before the merge? |
jeromekelleher
left a comment
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.
LGTM @ivan-krukov! I've gone through fairly carefully, and I don't see any show-stoppers.
There's some collatoral damage here from the merge where you've clobbered some recent metadata changes. You'll need to drop these from the diff (@benjeffery, any thoughts on the easiest way to do this?)
One thing we'll need to do as a follow up is to update simplify to keep track of the individual ID references in parents so that the IDs are correct afterwards.
Other than that, I think we just need to go through the standard steps for bumping file format version numbers and so on. These should all be done as follow ups, though, I think it's best to get these basic changes in soon so we don't have to keep rebasing them.
jeromekelleher
left a comment
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.
LGTM @ivan-krukov! One tiny nit left I think, otherwise good to squash and merge. The squash should go cleanly, now.
@benjeffery, can you open up some issues to track the remaining things that need to be addressed before we release please?
benjeffery
left a comment
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.
Great stuff, I've been through closely and logged issues for follow up work.
|
@ivan-krukov As @jeromekelleher said one nit about a comment that isn't consistent, then a squash and we can merge. |
|
@ivan-krukov, can we get this updated please? There's a significant chance of this PR getting out of date again if we don't merge it ASAP! |
3196c2b to
3d03c8c
Compare
|
I've just force-pushed a fix and squash to this PR. Will merge if all green. |
|
Segfault on some C tests - are you looking at this @benjeffery, or should @ivan-krukov pick it up? |
|
I'll check it out. |
3d03c8c to
0538515
Compare
|
The segfault was in the text parsing code for one of the example trees where the individuals string did not have parents ( |
0538515 to
8ebfd8b
Compare
|
I am so sorry that I am late for this. Thank you for resolving. |
|
Woohoo, great to see this merged! Thanks for all the hard work @ivan-krukov, adding new columns is always a marathon. (Thanks too @benjeffery!) |
No worries @ivan-krukov, it was a very small and quick fix. Thanks for the PR! |
Description
Adding a ragged
parentscolumn to theindividualstable.Fixes #852
This is a clean version of the #866 PR
PR Checklist: