Still problems showing conda environment

[richardjorne]

Dupe Check

• [X] I have searched Warp bugs and there are no duplicates

Describe the bug

after running conda activate llm, the (base) should change to (llm), but the new prompt is still (base).

To reproduce

Run conda activate [env name]

Expected behavior

No response

Screenshots

No response

Operating system

MacOS

Operating system and version

macOS Sonoma 14.5

Shell Version

No response

Current Warp version

No response

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[vorporeal]

Hey @richardjorne - what are you using for your prompt? Also, after you run conda activate llm, what's the output from running conda info?

[KoapT]

Same problem with you. Ever since I upgraded warp to the new version, this issue has been occurring.

[vorporeal]

Hey @KoapT - what shell are you using? Also, can you run conda info after activating your conda environment and post the output here?

[emmettng]

same problem here: macOS , zsh after activating a new env, the prompt is still (base) btw: this issue should have been fixed long time ago since python is a relatively popular language ... that's odd

[Gabriel-p]

Same here. My native terminal loads the ohmyzsh theme without issues and displays the conda environment correctly:

Warp loads the theme but does not display the loaded conda environment:

Here's the conda info output:

     active environment : asteca
    active env location : /home/gabriel/miniconda3/envs/asteca
            shell level : 1
       user config file : /home/gabriel/.condarc
 populated config files :
          conda version : 23.5.2
    conda-build version : not installed
         python version : 3.11.4.final.0
       virtual packages : __archspec=1=x86_64
                          __glibc=2.35=0
                          __linux=6.5.0=0
                          __unix=0=0
       base environment : /home/gabriel/miniconda3  (writable)
      conda av data dir : /home/gabriel/miniconda3/etc/conda
  conda av metadata url : None
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /home/gabriel/miniconda3/pkgs
                          /home/gabriel/.conda/pkgs
       envs directories : /home/gabriel/miniconda3/envs
                          /home/gabriel/.conda/envs
               platform : linux-64
             user-agent : conda/23.5.2 requests/2.29.0 CPython/3.11.4 Linux/6.5.0-44-generic elementary/7.1 glibc/2.35
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False

[KoapT]

Hey @KoapT - what shell are you using? Also, can you run conda info after activating your conda environment and post the output here?

Just the same like https://github.com/warpdotdev/Warp/issues/5151#issue-2422077668

[dannyneira]

I was able to reproduce this issue. I've noticed this only happens with a custom prompt, so I recommend the Warp prompt as a stopgap.

I'll let the team know and we'll post updates on this thread.

[Advait-M]

Hey @richardjorne @KoapT @emmettng @Gabriel-p!

I believe a related fix for Python's default venv setup may help resolve this issue as well (https://github.com/warpdotdev/Warp/issues/5122#issuecomment-2264437815). Could you please update to v0.2024.07.30.08.02.stable_01, and see if you're still running into any issues? Thanks for reporting!

[javiribera]

I'm getting the exact same issue with v0.2024.08.06.08.01.stable_00

[Advait-M]

I'm getting the exact same issue with v0.2024.08.06.08.01.stable_00

Gotcha - hmm yeah, conda still seems to be broken, though I expect it'll be a similar fix to Python's default virtualenv setup. I'll dig deeper into this later and update this thread.

Thanks for checking!

[Gabriel-p]

I'm getting the exact same issue with v0.2024.08.06.08.01.stable_00

Same here

[rlovell3]

I had the same issue with Warp not displaying my active conda env. In my case, I'm using I was using .oh-my-zsh with a custom theme. Rather than hope Warp gets to where I can continue to use my existing config, I chose to restore Warp to its default, and I must say that I am blown away with what you guys and gals set up as your default Warp prompt, and have no need to continue using my old configuration. For me, I'm gonna ride the Warp defaults train and watch with amazement. Change is good (and necessary) for survival.

[KoapT]

这是来自QQ邮箱的自动回复邮件。您好，我已收到您的邮件，会在阅读之后尽快给您回复。