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

New Issue

2fuL · 2021-11-24T12:17:42Z

2fuL commented

2021-11-24 12:17:42 +00:00

hello there.

with a fresh installation of tea version 0.8.0 I am not able to use it properly, examples:

Fresh install and create login to own instance

~/directory/REPO_OF_ORG $ tea login add
? URL of Gitea instance:  https://bla.bla.bla
? Name of new Login [bla.bla.bla]: bla.bla 
? Do you have an access token? No
? Username:  username
? Password:  ***************************************************************
? Set Optional settings:  No
Login as username on https://bla.bla.bla successful. Added this login as bla.bla

I am in a git repo I have on the server as well. In an organisation:

~/directory/REPO_OF_ORG $ tea pull
NOTE: no gitea login detected, falling back to login 'bla.bla'
Remote repository required: Specify ID via --repo or execute from a local git repo.

If I do it explicitly I get "some" result.. but there should be an Issues list, right?

~/directory/REPO_OF_ORG $ tea pull --repo amazing_tool/amazing_tool
NOTE: no gitea login detected, falling back to login 'bla.bla'
+-------+-------+-------+--------+-----------+---------+
| INDEX | TITLE | STATE | AUTHOR | MILESTONE | UPDATED |
+-------+-------+-------+--------+-----------+---------+
+-------+-------+-------+--------+-----------+---------+

If I change to a folder with a gitrepo I own personally on the server (not in Organisation I am In) I DON'T get the NOTE, but still no List

cd REPO_I_OWN
~/directory/REPO_I_OWN $ tea pulls
+-------+-------+-------+--------+-----------+---------+
| INDEX | TITLE | STATE | AUTHOR | MILESTONE | UPDATED |
+-------+-------+-------+--------+-----------+---------+
+-------+-------+-------+--------+-----------+---------+

However If I access an issue directly in this REPO_I_OWN I finally have success:

~/directory/REPO_I_OWN $ tea issue 1

   #1 isue number One blablba (closed)

  @ME created 2021-01-01 01:00

  • blabla

hello there. with a fresh installation of `tea version 0.8.0` I am not able to use it properly, examples: Fresh install and create login to own instance ``` ~/directory/REPO_OF_ORG $ tea login add ? URL of Gitea instance: https://bla.bla.bla ? Name of new Login [bla.bla.bla]: bla.bla ? Do you have an access token? No ? Username: username ? Password: *************************************************************** ? Set Optional settings: No Login as username on https://bla.bla.bla successful. Added this login as bla.bla ``` I am in a git repo I have on the server as well. In an organisation: ``` ~/directory/REPO_OF_ORG $ tea pull NOTE: no gitea login detected, falling back to login 'bla.bla' Remote repository required: Specify ID via --repo or execute from a local git repo. ``` If I do it explicitly I get "some" result.. but there should be an Issues list, right? ``` ~/directory/REPO_OF_ORG $ tea pull --repo amazing_tool/amazing_tool NOTE: no gitea login detected, falling back to login 'bla.bla' +-------+-------+-------+--------+-----------+---------+ | INDEX | TITLE | STATE | AUTHOR | MILESTONE | UPDATED | +-------+-------+-------+--------+-----------+---------+ +-------+-------+-------+--------+-----------+---------+ ``` If I change to a folder with a gitrepo I own personally on the server (not in Organisation I am In) I **DON'T** get the `NOTE`, but still no List ``` cd REPO_I_OWN ~/directory/REPO_I_OWN $ tea pulls +-------+-------+-------+--------+-----------+---------+ | INDEX | TITLE | STATE | AUTHOR | MILESTONE | UPDATED | +-------+-------+-------+--------+-----------+---------+ +-------+-------+-------+--------+-----------+---------+ ``` However If I access an issue directly in this `REPO_I_OWN` I finally have success: ``` ~/directory/REPO_I_OWN $ tea issue 1 #1 isue number One blablba (closed) @ME created 2021-01-01 01:00 • blabla ```

6543 added the

kind/bug

label 2021-12-02 21:38:22 +00:00

6543 commented

2021-12-02 21:39:02 +00:00

@2fuL It would help a lot if you could compile latest and test against it :)

noerw commented

2021-12-03 13:19:58 +00:00

About the org repo not found issue:
Could it be that your org repo doesn't have a branch named main, master or trunk?
Please provide the output of git remote -v and git branch -vv (and/or confirm that the host portion of the remote for the master/main/trunk branch matches the one that is configured for your tea login bla.bla).
About the empty listing: Are you sure there are open pull requests in the repo your user owns (not issues)? Does tea issues list content?
About the NOTE: no gitea login detected..., it would be nice if we'd supress this message, if a repo was explicitly given via --repo. (Though there's the problem that selecting a login is orthogonal to selecting a repo, not sure what's best here)

1. About the org repo not found issue: Could it be that your org repo doesn't have a branch named `main`, `master` or `trunk`? Please provide the output of `git remote -v` and `git branch -vv` (and/or confirm that the host portion of the remote for the `master`/`main`/`trunk` branch matches the one that is configured for your tea login `bla.bla`). 2. About the empty listing: Are you sure there are open *pull requests* in the repo your user owns (not *issues*)? Does `tea issues` list content? 3. About the `NOTE: no gitea login detected...`, it would be nice if we'd supress this message, if a repo was explicitly given via `--repo`. (Though there's the problem that selecting a login is orthogonal to selecting a repo, not sure what's best here)

2fuL commented

2021-12-08 10:07:27 +00:00

About the org repo not found issue:
Could it be that your org repo doesn't have a branch named main, master or trunk?
Please provide the output of git remote -v and git branch -vv (and/or confirm that the host portion of the remote for the master/main/trunk branch matches the one that is configured for your tea login bla.bla).

About the empty listing: Are you sure there are open pull requests in the repo your user owns (not issues)? Does tea issues list content?

About the NOTE: no gitea login detected..., it would be nice if we'd supress this message, if a repo was explicitly given via --repo. (Though there's the problem that selecting a login is orthogonal to selecting a repo, not sure what's best here)

Thank You for your hint:
The issue was that the remote repositories I use are accessed via ssh like

origin ssh://git@bla.bla/bla/blabla.git (fetch)
origin ssh://git@bla.bla/bla/blabla.git (push)

when I clone the repository with the http link given by gitea then tea works as expected.

Suggestion: create an option to fetch and push data over http in case origin is ssh

> 1. About the org repo not found issue: > Could it be that your org repo doesn't have a branch named `main`, `master` or `trunk`? > Please provide the output of `git remote -v` and `git branch -vv` (and/or confirm that the host portion of the remote for the `master`/`main`/`trunk` branch matches the one that is configured for your tea login `bla.bla`). > > 2. About the empty listing: Are you sure there are open *pull requests* in the repo your user owns (not *issues*)? Does `tea issues` list content? > > 3. About the `NOTE: no gitea login detected...`, it would be nice if we'd supress this message, if a repo was explicitly given via `--repo`. (Though there's the problem that selecting a login is orthogonal to selecting a repo, not sure what's best here) Thank You for your hint: The issue was that the remote repositories I use are accessed via `ssh` like ``` origin ssh://git@bla.bla/bla/blabla.git (fetch) origin ssh://git@bla.bla/bla/blabla.git (push) ``` when I clone the repository with the http link given by `gitea` then `tea` works as expected. Suggestion: create an option to fetch and push data over http in case origin is ssh

2fuL closed this issue

2021-12-08 10:07:27 +00:00

noerw commented

2021-12-11 16:57:43 +00:00

SSH origins should actually work fine, (in that the correct login and remote repo is detected from the git remote), so there might be a bug in tea.
Does the content of your tea login config field ssh_host (tea login edit) match the host in your git remote -v?
If no, this is a configuration error, if yes this is a bug.

SSH origins should actually work fine, (in that the correct login and remote repo is detected from the git remote), so there might be a bug in tea. Does the content of your tea login config field `ssh_host` (`tea login edit`) match the host in your `git remote -v`? If no, this is a configuration error, if yes this is a bug.

noerw reopened this issue

2021-12-11 16:57:43 +00:00

2fuL commented

2021-12-13 16:20:45 +00:00

Does the content of your tea login config field ssh_host (tea login edit) match the host in your git remote -v?

Yes it does match.

I am using a custom port though, so my git remote -v rather looks like:

ssh://git@host:12345/bla/blabla.git

while in ~/.config/tea/config.yml I don't see any Port mentioned.

> Does the content of your tea login config field `ssh_host` (`tea login edit`) match the host in your `git remote -v`? Yes it does match. I am using a custom port though, so my git remote -v rather looks like: `ssh://git@host:12345/bla/blabla.git` while in `~/.config/tea/config.yml` I don't see any Port mentioned.

noerw commented

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

Ah, if you use a nonstandard port, this is the same as #444 and #431, a regression from #391.
Looks like we really have to revert #391 (I just hope we don't break too many (already adapted) configs again by doing so..)

Will close this then, as we already track the issue.

Ah, if you use a nonstandard port, this is the same as #444 and #431, a regression from #391. Looks like we really have to revert #391 (I just hope we don't break too many (already adapted) configs again by doing so..) Will close this then, as we already track the issue.

noerw closed this issue

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

2fuL commented

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

Ah, if you use a nonstandard port, this is the same as #444 and #431, a regression from #391.
Looks like we really have to revert #391 (I just hope we don't break too many (already adapted) configs again by doing so..)

Will close this then, as we already track the issue.

Thank you.

After reading into this and changing in ~/.config/tea/config.yml: ssh_host from host to host:port tea works as expected :=)

> Ah, if you use a nonstandard port, this is the same as #444 and #431, a regression from #391. > Looks like we really have to revert #391 (I just hope we don't break too many (already adapted) configs again by doing so..) > > Will close this then, as we already track the issue. Thank you. After reading into this and changing in `~/.config/tea/config.yml`: `ssh_host` from `host` to `host:port` tea works as expected :=)

Sign in to join this conversation.

No Milestone

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/tea#446