Results 132 comments of Peter Kerpedjiev

@andywer What do you think of this PR? Anything I can do to make it more palatable?

Hey, sorry, I'm a little delayed in writing a test. While I dawdle on that, just wanted to say that I am actively using that approach and so far it's...

Thanks for reporting this and sorry for the delayed reply. AFAICT, we need to update higlass to use a later version of React. This is something we should've done a...

The code to add support for v3 is actually merged, we just haven't released it yet: https://github.com/higlass/higlass-python/pull/80 There will be a release in the next few days.

Oh, good point. I have not. That MR only addresses the React issue in the JS. Perhaps v3 support is not that close.

I think the issue is the HorizontalChromosomeLabels track: http://higlass.io/l/?d=dneW8uRKQQ6h8Hnj_v_cMw

Because it's awful and needs to be rewritten and/or fixed 🤷‍♂

We're spending a bunch of time and allocating a ton of memory in `drawTicks`: ![image](https://user-images.githubusercontent.com/2143629/73032027-abaf6500-3df2-11ea-81fe-0797fc1ee292.png)

I thought we fixed that... are you using the latest version of the client? If so, then I'd monitor the memory used by higlass. I think this is a symptom...

I think it's actually just this block of code: https://github.com/higlass/higlass/pull/840/files#diff-b5faaa986ed69db6036edb97717f219aR329 Lines (329 - 342). But that whole PR should be fine to merge.