tide

tide copied to clipboard

Describe the bug

After installing the package I started getting this message when opening the terminal (terminal or iterm):

Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe

As far as I can see, everything works fine, but couldn't finde the solution on my own.

Steps to reproduce

1. Install fish
2. Install fisher
3. Install tide

Environment

• Operating system: Mac Os 10.15.5
• Terminal emulator: Iterm2

Additional context

Sorry for the late reply. I think I've seen this once before, it has to do with writing to the universal variable file, but I don't know much more 😞

Same here on Ubuntu 20.04

Closing as stale; Fish 3.3 released and almost no one has reported this issue.

Same here on Ubuntu 20.04 WSL2, fish 3.3.1

Can also confirm on Ubuntu 20.04, fish 3.3.1.

This can be reproduced by fast tapping some ENTERs.

I'm having the same issue after update to

fish, version 3.3.1
tide, version 5.0.1

Reinstalling tide by insert fisher update IlanCosman/tide into config.fish fixed the problem.

@smthpickboy What's the difference by putting fisher update ilanCosman/tide instead of doing it manually?

I updated to 5.0.1 manually, the issue still persists.

@smthpickboy What's the difference by putting fisher update ilanCosman/tide instead of doing it manually?

I updated to 5.0.1 manually, the issue still persists.

No difference. But when the problem happened, my shell simply couldn't start. So I have to put it in config.fish.

Are any of you using Conda?

Are any of you using Conda?

I have miniconda installed

I am using conda, too.

Alright yeah, this bug is coming from my ancient nemesis Conda 😂 I'll see if I can do anything about it.

This can be reproduced by fast tapping some ENTERs.

Facing the same issue, any solutions yet? Thanks!

Yes, you can solve this problem by adding status is-interactive && before the conda init:

# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
status is-interactive && eval /Users/ilan/opt/anaconda3/bin/conda "shell.fish" "hook" $argv | source
# <<< conda initialize <<<

Yes, you can solve this problem by adding status is-interactive && before the conda init:

# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
status is-interactive && eval /Users/ilan/opt/anaconda3/bin/conda "shell.fish" "hook" $argv | source
# <<< conda initialize <<<

Confirmed that it works!

I'm seeing this issue without conda. I'm using pyenv and pipenv