Incompatible with 2025.1

[AkibaAT]

Is there an existing issue for this?

• I have searched the existing issues

Are you sure that this bug is related to this DDEV Integration Plugin?

• I am sure

Enter your error report ID (If available)

No response

Describe the bug

The plugin is not compatible with 2025.1, currently available as EAP.

Steps to reproduce

No response

Additional context

No response

[AkibaAT]

After some preliminary testing, it seems that WSL use is currently broken. The file picker to set the DDEV binary doesn't allow navigating to the WSL storage in 2025.1 currently. Since this also affects PhpStorm's built-in functions such as selecting the composer.json in the project, the current EAP is not usable for my own setup.

Additionally, the docker plugin throws an exception on opening a project. I'll revisit with future EAPs, right now it's too early.

[rfay]

Thanks so much for tracking these things and chasing this down! Did you open a ticket with Jetbrains?

[AkibaAT]

Thanks so much for tracking these things and chasing this down! Did you open a ticket with Jetbrains?

I did not, but I checked that there is already one open there. The new version uses the native file browser by default.
There's also been an update to the EAP that I didn't check out yet.

[AkibaAT]

Here's a first build for the current EAP. It contains no changes yet apart from increasing the IDE version and disabling searchable options for the build to pass:
ddev-intellij-plugin-0.0.1-dev.zip

DDEV plugin wise, things seem to work normally. Deprecations will have to be fixed, but at least the functionality looks to be intact.

IDE wise however, there seems to be a good list of JetBrains side issues with the rework of the file browser handling. Opening a project on WSL with my Windows installation of PhpStorm, none of my database connections work, only giving me a "No such file or directory" error, with no hint as to what it even tried to open.

I had guessed that maybe it was the Keepass setting, as that notably now opens up a Windows file browser instead of the WSL file browser, but even setting passwords to temporary didn't eliminate the error, so maybe the issue is somewhere else entirely.

Opening the same project via a WSL remote installation however, no issues, and things seem to be working normally.

[rfay]

@AkibaAT do you still not have privs to make a pre-release? @nico-loeber would you mind giving them to @AkibaAT ?

[AkibaAT]

@AkibaAT do you still not have privs to make a pre-release? @nico-loeber would you mind giving them to @AkibaAT ?

I've not heard anything from @nico-loeber yet since last November during the merges for the last version.

Digging a little deeper into the IDE issues, it looks like it's getting very confused, and tries to open sockets in a Windows path, when the project itself resides on WSL:

Or maybe that's a red herring, and the actual cause it it trying so hard to find its own java anywhere within all of my PATH:

I'll have to try to sift through the JetBrains issues tracker for this later.