Potential threading issues

[Luro02]

Based on my regular use, I observed some issues that are difficult to reproduce/only happen sporadically/without an obvious solution:

• When Intelligrade is started and some crash occurs, it will not be the only one. There is another crash triggered by some slow operation running on the EDT (= UI) thread. See https://plugins.jetbrains.com/docs/intellij/threading-model.html
• The maven project is not always loaded, same for the automatic SDK setup, introduced with Implement some quality-of-life features #102. I guess the reason is that it hasn't finished loading yet, resulting in the code trying to load a maven project that is not loadable yet? Maybe some code that periodically checks until the project is loaded could work?
• In rare instances the clone command might fail, because of existing files/something that could not be deleted.

[Feuermagier]

Some thoughts:

1. I'm not sure what causes this. Do you have a stack trace for the timeout? This could also be due to the current IJ version being quite buggy (I sometimes also get these timeouts also in normal IJ and CLion)

2. In theory this should not happen, since the Maven load only starts after file synchronization is done:

   intelligrade/src/main/java/edu/kit/kastel/sdq/intelligrade/state/PluginState.java

   Lines 358 to 361 in 0dfa736

   	IntellijUtil.forceFilesSync(() -> {
   	// Force IntelliJ to update the Maven project
   	IntellijUtil.getMavenManager().forceUpdateAllProjectsOrFindAllAvailablePomFiles();
   	});

   
   Though I know that this happens quite frequently in practice, so it might be worth looking into it

3. This typically happens when IJ manages to recreates the IDE files between deleting the contents of the project directory and cloning the submission. I think a simple solution would be to clone the submission into a subfolder of the project directory, which can be cleared/deleted without issue.

[Luro02]

I'm not sure what causes this. Do you have a stack trace for the timeout?

I am not sure either, there is a stacktrace, but only for intellij and swing components. Might really be an issue with intellij, I just wanted to keep track of it here.