Colin Diesh

I went ahead and released as @gmod/[email protected] It looks like maybe the washu has a vendored version of @gmod/bbi or different implementation but feel free to check out the fix...

this is related to the following sort of technical detail LinearGenomeViewModel.activateTrackSelector calls -> session.addWidget -> which then clears away any existing state (such as collapsed state) in the track selector...

after pondering this a bit, i think saving and restoring collapsed state from localstorage may be a good option

this link https://stackoverflow.com/questions/64782261/best-approach-to-wait-on-material-ui-ripples-to-complete-before-taking-snapshots suggests running jest.runAllTimers. could help but it is a lot of extra work to do across all our tests. alternative option could be to disable touch ripples...

i haven't seen this so close for now random note: something related was mentioned in mui v6 release notes, so can revisit if it occurs again https://mui.com/material-ui/migration/upgrade-to-v6/

if you are able to can you send the GFF file? there are a couple reasons for this off the top of my head why this could happen but it...

thanks for sending it. I believe that if you update your config to have this specific dontRedispatch line, then it should fix the issue you are seeing ``` { "type":...

can you confirm that the dontRedispatch setting is active by going to the about track and showing that it is listed? e.g. it is listed here  if it is...

Now I am a bit mystified...it would be quite weird if the "gff parser bufferSize" was actually an issue in this case becuase the parseStringSync function of our Gff3TabixAdapter uses...

very interesting...I don't have a clue yet but I'll keep brainstorming. it is funny that I can't reproduce it (even tried the URLs that you posted directly in case it...