tea pr checkout fails with path "segment [0] is empty" #444

New Issue

plafue · 2021-11-15T21:09:02Z

plafue commented

2021-11-15 21:09:02 +00:00

I'm using tea 0.8.0 and gitea 1.15.6.

The ssh server I use for git listens on a port other than 22. Tea seems to ignore .ss/config, so I tried to add the port to ssh_host as suggested in #431 (comment) .

After doing that I don't get the no route to host error anymore, but the following:

$ tea pr checkout 1
Error: couldn't fetch PR: path segment [0] is empty

I also tried adding the port explicitly in ~/.git/config (and removing the host specific configuration from ~/.ssh/config), which lead to the same error above, while git commands continued working correctly.

I'm using tea `0.8.0` and gitea `1.15.6`. The ssh server I use for git listens on a port other than `22`. Tea seems to ignore `.ss/config`, so I tried to add the port to ssh_host as suggested in https://gitea.com/gitea/tea/issues/431#issuecomment-593348 . After doing that I don't get the `no route to host` error anymore, but the following: ``` $ tea pr checkout 1 Error: couldn't fetch PR: path segment [0] is empty ``` I also tried adding the port explicitly in `~/.git/config` (and removing the host specific configuration from `~/.ssh/config`), which lead to the same error above, while `git` commands continued working correctly.

noerw added the

kind/bug

label 2021-11-19 11:25:33 +00:00

noerw commented

2021-11-19 11:43:23 +00:00

Oh no.
Can you send us the (redacted) output of git remote -v in the repo where you ran that command?
And also the (redacted) tea config?
Thanks

Oh no. Can you send us the (redacted) output of `git remote -v` in the repo where you ran that command? And also the (redacted) tea config? Thanks

plafue commented

2021-11-19 12:20:13 +00:00

Hey @noerw thanks for the reply!

≻  git remote -v
origin  gitea@${REMOTE}:test/test.git (fetch)
origin  gitea@${REMOTE}:test/test.git (push)

Here are the contents of ~/.config/tea/config.yml. There were no trailing slashes in any occurence of ${REMOTE}, just in case you were wondering.

logins:
- name: ${REMOTE}
  url: https://${REMOTE}
  token: ${TOKEN}
  default: false
  ssh_host: ${REMOTE}
  ssh_key: /home/plafue/.ssh/id_rsa
  insecure: false
  user: plafue
  created: 1636976517

I can also provide access to the repo if it helps debugging.

Hey @noerw thanks for the reply! ```shell ≻ git remote -v origin gitea@${REMOTE}:test/test.git (fetch) origin gitea@${REMOTE}:test/test.git (push) ``` Here are the contents of `~/.config/tea/config.yml`. There were no trailing slashes in any occurence of `${REMOTE}`, just in case you were wondering. ```yaml logins: - name: ${REMOTE} url: https://${REMOTE} token: ${TOKEN} default: false ssh_host: ${REMOTE} ssh_key: /home/plafue/.ssh/id_rsa insecure: false user: plafue created: 1636976517 ``` I can also provide access to the repo if it helps debugging.

plafue commented

2021-11-19 12:34:19 +00:00

The error reported in this issue happens as soon as I add a port to the ssh_host line e.g. ssh_host: ${REMOTE}:3333

The error reported in this issue happens as soon as I add a port to the `ssh_host` line e.g. `ssh_host: ${REMOTE}:3333`

noerw commented

2021-11-19 13:13:05 +00:00

I see, thanks. I assume it will work when you set REMOTE=${REMOTE}:3333 for your git remote configuration and tea ssh_host value (i.e. don't rely on ~/.ssh/config & ~/.gitconfig).
tea embeds its own clients for ssh and git, and it seems they don't make use of that config.
Not sure if it's simpler to add support for these configs to the client libraries, or to switch to native git..

Did this setup work for you with tea 0.7? If so, we may need to revert #391.

I see, thanks. I assume it will work when you set `REMOTE=${REMOTE}:3333` for your git remote configuration and tea `ssh_host` value (i.e. don't rely on `~/.ssh/config` & `~/.gitconfig`). tea embeds its own clients for ssh and git, and it seems they don't make use of that config. Not sure if it's simpler to add support for these configs to the client libraries, or to switch to native git.. Did this setup work for you with tea 0.7? If so, we may need to revert #391.

noerw commented

2021-11-19 13:13:55 +00:00

Nonetheless, the error path segment [0] is empty shouldn't ever be thrown, there's an issue in the URL parsing to be fixed (fwiw: I currently don't have time to work on tea)

Nonetheless, the error `path segment [0] is empty` shouldn't ever be thrown, there's an issue in the URL parsing to be fixed (fwiw: I currently don't have time to work on tea)

plafue commented

2021-11-19 14:00:42 +00:00

I see, thanks. I assume it will work when you set REMOTE=${REMOTE}:3333 for your git remote configuration and tea ssh_host value (i.e. don't rely on ~/.ssh/config & ~/.gitconfig).

I tried that too and didn't work. I will give a try to v0.7 once I have some time.

fwiw: I currently don't have time to work on te

I appreciate that you take the time to even reply.

> I see, thanks. I assume it will work when you set REMOTE=${REMOTE}:3333 for your git remote configuration and tea ssh_host value (i.e. don't rely on ~/.ssh/config & ~/.gitconfig). I tried that too and didn't work. I will give a try to v0.7 once I have some time. > fwiw: I currently don't have time to work on te I appreciate that you take the time to even reply.

plafue closed this issue

2021-11-19 14:07:12 +00:00

plafue reopened this issue

2021-11-19 14:07:18 +00:00

plafue commented

2021-11-19 14:10:42 +00:00

Using 0.7.1 and setting teas configuration to ssh_host: ${REMOTE}:3333 leads to a 404:

≻  ~/Downloads/tea-0.7.1-linux-amd64 pr checkout 1
Error: 404 Not Found

Using 0.7.1 and setting teas configuration to `ssh_host: ${REMOTE}:3333` leads to a 404: ``` ≻ ~/Downloads/tea-0.7.1-linux-amd64 pr checkout 1 Error: 404 Not Found ```

noerw referenced this issue

2021-12-14 15:46:52 +00:00

fresh install of tea no pull from ORGs, no issue list #446

2fuL referenced this issue

2021-12-15 17:00:15 +00:00

fresh install of tea no pull from ORGs, no issue list #446

noerw commented

2021-12-23 14:04:40 +00:00

to add: running tea repo fork without local repo context also returns Error: path segment [0] is empty

to add: running `tea repo fork` without local repo context also returns `Error: path segment [0] is empty`

😕 1

noerw referenced this issue