Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Sort using mutation.parent property
See original GitHub issueCurrently sort_tables doesn’t ensure mutations occur after their parents. It probably should, but this behvaior is documented, so it’s not major.
This is a way that tables can be out of order that sort_tables does not fix, so we should probably address it, although we don’t have a use case that produces tables out of order in this way.
The only way I can think of to do this is to add a field to the mutation struct used for sorting that is “number of hops to the root”, computed by following mutation.parent indices until you hit a -1.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ping @Chris1221 as an issue that could probably be tackled along with https://github.com/tskit-dev/tskit/issues/117 (I would find it useful if this issue were solved)
Probably not for 0.6.1 I’d say — shall we create a 0.6.2 milestone and add it to that?