-
Notifications
You must be signed in to change notification settings - Fork 68
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
cpg-console error about kotlin version #2029
Comments
Unfortunately the console is hard to maintain, since ki-shell is semi unmaintained by JetBrains and is still running Kotlin 1.9. In the long run we want to explore other options and it looks like it broke again without us noticing :( Maybe this will be the final nail on the coffin for the console. |
I tried compiling cpg with kotlin 1.9 but it did not work. I think the cpg-console is quite an important component for the users trying to explore this tool. thanks! |
Ok it seems you can just ignore this error. The analysis still works (although with more warnings).
|
I am trying to follow the tutorial https://github.com/Fraunhofer-AISEC/cpg/blob/main/tutorial.md but it seems updated as some commands are not available anymore.
is the thanks! |
The commands are still valid, but it seems like that even though we explicitly tried to stay in Kotlin 2.0.X, somehow some kotlin dependencies updated themselves to Kotlin 2.1.0 and because the console uses ki-shell and ki-shell does not work with 2.10 (see Kotlin/kotlin-interactive-shell#131), we are stuck here :( In the long run the only viable option would be to replace the shell altogether, unfortunately there is not really something available in terms of a good Kotlin REPL that we can just use as a dependency :( |
Runtime errors due to incompatible kotlin compiler. It seems a regression of #1272 or that fix was incomplete.
I am on latest commit 0d28981 running openjdk 17 on ubuntu machine.
After building with I with
./gradlew clean :cpg-console:installDist
I get the following error at runtime.The text was updated successfully, but these errors were encountered: