cancel old http requests / don't display old results that are no longer active filters

[yochannah]

I just ran a query that took a long time to return (which is fine, sometimes that just happens) and I got bored waiting for it to return. The search was a chromosome location search over something like 3:2098000-3059999. It might be faster now that it's been run on the server once?

Once I clicked reset I went and started to filter down a dataset.... and then the chromosome results came back, and updated the view! The screenshot below is definitely the results for genes in the chromosome search - see http://www.humanmine.org/humanmine/report.do?id=1264327 as an example.

We might need to do something like keeping track of which results are returned and whether or not they're still relevant. If this is tricky let me know your thoughts!

[AdrianBZG]

@yochannah Just a question, when doing that, you got a error in console like "Did not remove a single constraint" ??

[AdrianBZG]

@yochannah I'm still trying to reproduce this, but im unable to 😢

[yochannah]

Whoops! It's okay to ignore it until I'm back in the office

On Sun, 8 Jul 2018, 22:34 Adrián Bazaga, notifications@github.com wrote:

@yochannah https://github.com/yochannah I'm still trying to reproduce this, but im unable to 😢

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/AdrianBZG/InterMine-Data-Browser-Tool/issues/51#issuecomment-403318953, or mute the thread https://github.com/notifications/unsubscribe-auth/AI14jmjGHV7ZEPj72ZLh4rh7-wZ78wpwks5uEnrUgaJpZM4VD1GG .

[AdrianBZG]

@yochannah Ok! I hope we will manage to spot this bug when you are back 🤓

[yochannah]

I'll re-open this if I can reproduce it