Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuring time.FORMAT breaks ssh #1517

Closed
2 of 7 tasks
mnsh opened this issue Apr 20, 2017 · 4 comments
Closed
2 of 7 tasks

Configuring time.FORMAT breaks ssh #1517

mnsh opened this issue Apr 20, 2017 · 4 comments
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/bug

Comments

@mnsh
Copy link
Contributor

mnsh commented Apr 20, 2017

  • Gitea version (or commit ref): a2d365c
  • Git version: 2.11.0
  • Operating system: CentOS-6.9
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Lately SSH access to a gitea instance of ours tracking the master branch has been broken. Doing a clone or pull over ssh simply hangs, with gitea serv key-X --conf=... blocking on waitid(...) and it's spawned git-upload-pack org/repo.git blocking on read(0, ...).

After a little digging, I tried running the expected gitea serv ... command as the gitea user:

$ SSH_ORIGINAL_COMMAND="git-upload-pack '/org/test.git'" /usr/local/bin/gitea serv key-1 --config=/path/to/conf/app.ini
2017/04/20 03:45:15 [T] Custom TimeFormat: 2006-01-02 15:04:05 CET
00f263b78e06ee70f741ce1360f5c6c2e15a09df4d3e HEADmulti_ack thin-pack side-band side-band-64k ofs-delta shallow deepen-since deepen-not deepen-relative no-progress include-tag multi_ack_detailed symref=HEAD:refs/heads/master agent=git/2.11.0
003f63b78e06ee70f741ce1360f5c6c2e15a09df4d3e refs/heads/master
0000

The first line in the output is causing the problem - it's written to stdout, which git expects to "own".

Commenting out [time] -> FORMAT in the configuration or commenting out the log.Trace("...")-call in modules/setting/setting.go restores SSH access to gitea.

@lunny lunny added the type/bug label Apr 20, 2017
@lunny lunny added this to the 1.2.0 milestone Apr 20, 2017
lunny added a commit to lunny/gitea that referenced this issue Apr 20, 2017
@lunny lunny modified the milestones: 1.3.0, 1.2.0 May 25, 2017
@lunny lunny modified the milestones: 1.3.0, 1.x.x Oct 17, 2017
@stale
Copy link

stale bot commented Feb 11, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Feb 11, 2019
@ptman
Copy link
Contributor

ptman commented Feb 12, 2019

this is quite annoying

@stale stale bot removed the issue/stale label Feb 12, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Feb 12, 2019
@zeripath
Copy link
Contributor

Hi is this still happening in 1.8?

I thought I'd got upload pack et al to be truly quiet in #5887.

If it's still happening I should be able to fix.

@zeripath zeripath added issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail and removed issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented labels May 27, 2019
@lunny lunny removed this from the 1.x.x milestone Jun 9, 2019
@mnsh
Copy link
Contributor Author

mnsh commented Jun 25, 2019

Hi is this still happening in 1.8?

I thought I'd got upload pack et al to be truly quiet in #5887.

If it's still happening I should be able to fix.

For the record: with current master, this is no longer an issue.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants