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.

Sign up for GitHub

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

Jump to bottom

Repository home page show error file last commit message. #3202

Closed
lunny opened this issue Dec 15, 2017 · 5 comments
Closed

Repository home page show error file last commit message. #3202

lunny opened this issue Dec 15, 2017 · 5 comments
Labels
issue/critical This issue should be fixed ASAP. If it is a PR, the PR should be merged ASAP type/bug
Milestone
1.4.0

Comments

@lunny
Copy link
Member

lunny commented Dec 15, 2017 •
edited
Loading

Compare github's home page
https://github.com/go-gitea/gitea/tree/release/v1.0
image

vs https://try.gitea.io/gitea/gitea/src/branch/release/v1.0
image
@lunny lunny added type/bug issue/critical This issue should be fixed ASAP. If it is a PR, the PR should be merged ASAP labels Dec 15, 2017
@lunny lunny added this to the 1.4.0 milestone Dec 15, 2017
@ethantkoenig
Copy link
Member

Possibly related to go-gitea/git#91. I will investigate as soon as I get the chance.

@ethantkoenig ethantkoenig mentioned this issue Dec 15, 2017
Closed
7 tasks
@lunny
Copy link
Member Author

lunny commented Dec 16, 2017

Repo.cache will be invoked in multiple go routines.

@lunny
Copy link
Member Author

lunny commented Dec 16, 2017

Maybe add a test some commit tree the same as github.

@lunny
Copy link
Member Author

lunny commented Dec 16, 2017

Confirmed release/v1.3 has no this issue.

This was referenced Dec 16, 2017
Merged
Closed
@lunny
Copy link
Member Author

lunny commented Dec 20, 2017

resolved by #3240

@lunny lunny closed this as completed Dec 20, 2017
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/critical This issue should be fixed ASAP. If it is a PR, the PR should be merged ASAP type/bug
Projects
None yet
Milestone
1.4.0
Development

No branches or pull requests
2 participants
@lunny @ethantkoenig