You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! The QLInspector you provided is extremely useful and has been a great help to me. However, I don't understand why the other four QL files you provided can all display results normally in VSCode, while using QLInspector.ql (not the Old version) gets stuck at the "showing results" progress in VSCode. I even went to sleep and woke up, but it still hadn't loaded.
I wonder if this is related to the complexity of the database I generated? My CodeQL database was generated using another open-source project: https://github.com/waderwu/extractor-java, and the database generation process was also quite slow! If a project uses many dependencies in its pom.xml, I download the dependency code from Maven or GitHub (and if there's no alternative, I decompile the JAR files) to participate in the CodeQL database generation, which makes the database generation process slow as well.
However, apart from this extractor-java tool that can generate a CodeQL database without compilation, I haven't found a better way to generate a complete QL database without encountering errors. If you have any better ideas, I would greatly appreciate your guidance!
The text was updated successfully, but these errors were encountered:
Hi @Potatowo233 that's my fault I forgot to add CodeQL metadata to the query, I've made a new commit you can just git pull and re-run the query.
I'm not sure to understand do you already have a codeql database of your project ? If no there are recent changes with codeql that should allow you to build a database even If you can't build all the components. You first need to decompile your jar (I like to use the decompiler from InteliJ and then run the database creation with --build-mode none:
Hello! The QLInspector you provided is extremely useful and has been a great help to me. However, I don't understand why the other four QL files you provided can all display results normally in VSCode, while using QLInspector.ql (not the Old version) gets stuck at the "showing results" progress in VSCode. I even went to sleep and woke up, but it still hadn't loaded.
I wonder if this is related to the complexity of the database I generated? My CodeQL database was generated using another open-source project: https://github.com/waderwu/extractor-java, and the database generation process was also quite slow! If a project uses many dependencies in its pom.xml, I download the dependency code from Maven or GitHub (and if there's no alternative, I decompile the JAR files) to participate in the CodeQL database generation, which makes the database generation process slow as well.
However, apart from this extractor-java tool that can generate a CodeQL database without compilation, I haven't found a better way to generate a complete QL database without encountering errors. If you have any better ideas, I would greatly appreciate your guidance!

The text was updated successfully, but these errors were encountered: