New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQLancer fails to load providers when using a newer JVM #799
Comments
Was this happening when launching sqlancer in Eclipse? |
Yes, I've updated the issue description already. |
Sounds like that Eclipse's inserted some debug/diagnosis args. What's the actual arguments that the main function get? |
Here is the full command line for WSL+Ubuntu (I can also reproduce this on Ubuntu directly).
|
as in #800 (review),
Here's information in Idea:
|
When using SQLancer with the JVM below (e.g., using a command such as
java -jar sqlancer-2.0.0.jar duckdb
), everything seems to work fine.If I now use the JVM below, I get a
ParameterException
as shown further below.Edit: This is the JDK used by the latest Eclipse, to which I imported SQLancer as a Maven project. Perhaps the issue could be environment-specific.
This seems related to the
ServiceLoader
that we are using. Starting SQLancer with no options (java -jar sqlancer-2.0.0.jar
) shows that no providers were loaded since only general options are shown:A workaround is to use an older Java version (e.g., Java 11). Another workaround would be to manually add the providers. For example, above line 612 in the main class (see
sqlancer/src/sqlancer/Main.java
Line 612 in e418489
providers.add(new DuckDBProvider());
. Neither is a satisfactory long-term solution, so we should fix this.The text was updated successfully, but these errors were encountered: