ashald / EnvFile

EnvFile 3.x is a plugin for JetBrains IDEs that allows you to set environment variables for your run configurations from one or multiple files.
MIT License
533 stars 125 forks source link

Issues when using with IntelliJ 2023.1 #217

Open ondrejfuhrer opened 1 year ago

ondrejfuhrer commented 1 year ago

When updated to the latest version (2023.1) I have an issue with the plugin.

It seems to be not working properly (I get an error on missing env variables), however I also can't see any error anywhere. Anyone else experiencing this?

olegorsha commented 1 year ago

Confirm. After the update to 2023.1, the values of variables in the file are ignored.

velykov commented 1 year ago

In IntelliJ IDEA 2022.3.3 cannot find any place for configure plugin.

HWiese1980 commented 1 year ago

Confirmed. Plugin version 3.4.1, IntelliJ IDEA Build #IU-223.8617.56, built on January 26, 2023

Amimul1234 commented 1 year ago

yeap....on intellij idea ultimate 23.1 the env file plugin is not loading the variables.

HWiese1980 commented 1 year ago

@ashald Could you please confirm looking into this? It's a critical bug in my opinion.

ashald commented 1 year ago

I'm not looking into this currently as I'm on vacation. Would welcome contributions though.

HWiese1980 commented 1 year ago

I'm not looking into this currently as I'm on vacation. Would welcome contributions though.

Fine with me. Enjoy your trip!

So if anyone else got the time to, I'd be very happy 👍

HWiese1980 commented 1 year ago

Two weeks later, what's the status? Still on vacation, @ashald?

HWiese1980 commented 1 year ago

I would really appreciate a fix as this is the only plugin of its kind. I do not know how to write plugins for IntelliJ and it would take me a tremendous amount of time to get my head into it. Time that I do not have. I'd be really grateful if someone could fix this problem! It's a real shame that the plugin is currently not working at all.

Kavan72 commented 1 year ago

@HWiese1980 i'm using latest version of IntelliJ IDEA 2023.1.1 (Ultimate Edition) Build #IU-231.8770.65, built on April 27, 2023, and working fine for me

cmeury commented 1 year ago

Can confirm as well, works with Build #IU-231.8770.65, built on April 27, 2023.

ondrejfuhrer commented 1 year ago

I can also confirm that the issue is only with the previous version. After upgrading to 2023.1.1 it seems to work as expected.

HWiese1980 commented 1 year ago

I'll have to check.

mrichards01 commented 1 year ago

Intellij Version 2023.1.1, Build #IC-231.8770.65 also works for me on trivial examples.

Chris-May commented 1 year ago

It works for me on any configuration I created in an older version, but it is still broken on PyCharm 2023.1.1 (Professional Edition) Build #PY-231.8770.66, built on April 27, 2023

Something tells me this is on JetBrains' side.

jbonfardeci commented 1 year ago

The only way I could get IntelliJ 2023.1.2 (Ultimate) to recognize environment variables in my ~/.bashrc, was to set an environment variable to the $HOME/idea-IU-231.9011.34/binfolder. The from the terminal running nohup idea.sh > idea.log will use the environment variables ~/.bashrc for that session.

DelboyJay commented 1 year ago

I can confirm this works on PyCharm 2023.1.2 Professional for Linux (Zorin16) but the same PyCharm version is broken on a MacOS V13.4 M1 Apple Silicon. I'm using EnvFile 3.4.1 on both systems. update - My colleague is running the same versions on the same laptop and his is working so I must have a config issue somewhere.

vm137 commented 10 months ago

Confirm IntelliJ IDEA 2023.2.1 (Ultimate Edition) EnvFile 3.4.1 plugin fails to work with error message in popup.

thezerobit commented 8 months ago

In PyCharm 2023.2.3 I noticed that is was not working on an older project, but it did work on newer projects. To get it working on the older project, I had to close it, delete the .idea folder and create a new project. Before doing this, I tried removing and reinstalling the Plugin and restarting PyCharm. Nothing would get it work and I double and triple checked the configuration, disabled and enabled the plugin and created many new run configurations. Very frustrating, but I'm glad I found a workaround because this plugin is essential.