Error when running commands on remote servers

Open
#2,931 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
bash, zsh
Domain
cli

Research direction

Reproduce the problem by SSHing into a remote host and sourcing /path/to/.zsh_functions, then inspect how Warp handles the warp_preexec hook and the referenced .zshrc context. Done means the command works on remote servers without the reported error while continuing to work locally; the issue names no source files or tests.

Written by the indexing model from the issue text.

Description

bug ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

For context this issue started after uninstalling oh my zsh from my computer.

When I run commands on a remote server I receive the error "warp_preexec:local:1: not valid in this context: path/to/.zshrc"

Example command
source /path/to/.zsh_functions

Same command run just fine locally.

To Reproduce

ssh into remote host

run command
source /path/to/.zsh_functions

Expected behavior

No response

Screenshots
image
Operating System

None

OS Version

13.3.1

Shell Version

zsh 5.9 (x86_64-apple-darwin22.0) | GNU bash, version 3.2.57(1)-release (arm64-apple-darwin22)

Warp Version

v0.2023.04.11.08.03.stable_00

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:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.