Tab title showing another device name (that exists in the network)

Open
#3,053 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos, rust, zsh

Research direction

Start by reproducing the new-tab behavior on macOS 13.2.1 with zsh while another publicly discoverable device is on the network, and compare the displayed name with the computer name. Trace the tab-title and hostname selection entry point; done means the new tab consistently shows the local computer name rather than another network device.

Written by the indexing model from the issue text.

Description

area:window-tabs-panes bug needs-info ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

When I open a new tab, it's showing a computer name that has nothing to do with my computer name, but that actually exists in the network I'm connected.

You can see it in the screenshots

To Reproduce
  1. Be connected in a network with other devices that are publicly discoverable
  2. Click on + to open a new tab
Expected behavior

It should show the name of my computer.

Screenshots

What the tab name is showing
image

What the actual name should be
Screenshot 2023-05-11 at 14 42 15

Operating System

MacOS

Operating System and Version

13.2.1

Shell Version

zsh 5.8.1 (x86_64-apple-darwin22.0)

Warp Version

v0.2023.03.07.08.02.stable_03

Additional context

No response

Does this block you from using Warp daily?

No

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.