Andrew Konstantinov

There is another issue for global search: https://github.com/doyensec/inql/issues/68 Adding two search fields might be confusing though. Can they be integrated into a single search field?

So, here's the status on this bug. The root cause is a 3rd party library stickytape. It's a known issue and we actually don't use this library at all in...

Hey @bandronic and thanks for contributing! I'm a little puzzled about the commit c99e6763705c97cfb94ac0570432b0f9e51ea161, as nothing seems to be using this new library. Can you explain the reason for adding...

We'll start the rewrite in August and we'll try to keep it 1:1 or as close as possible to the existing Python code. So, I'd say if you see other...

Oh, that's a great feature! Might be relevant: we have a plan to generate queries with variables (#77), although I'm still not sure about UI. The pull request is good!...

Thanks, it's clearly a bug in InQL and I'll look into it. Btw, if you notice any other issues when going through Portswigger labs (or get ideas for feature requests),...

Thank you for the report! The Activity query alone takes 2 minutes to get parsed on my machine. I filed the issue with GQLSpection, will take a look at optimizations...

So, this turned out to be way more complicated than I initially thought. I'm planning to address the performance issue by reducing recursion to an iterative loop and generating queries...

I replaced the recursion with a loop and the parsing time for the whole h1 schema (on my machine) now is under 2 minutes. I will try to reduce this...

Well, after replacing recursive query generation with iterative version in #33 the query generation went down from 2 minutes to a couple of seconds. The depth calculation was adjusted as...