Closed vw98075 closed 3 years ago
please test against v1.15.0-rc2
$ echo "49ad088b8" | git cat-file --batch
49ad088b8 missing
49ad088b8
does not refer to a commit, tag, or tree in Gitea's repository.
I just did
git fetch upstream
Its version is 1.15.0+dev-591-g49ad088b8. The bug still exists. I don't know whether I get the latest version or not. The upstream is https://github.com/go-gitea/gitea.git.
At the time of me writing this comment the current HEAD of main is 370516883. The current head of release/v1.15 is 840d240a6 and is 614 commits after v1.15.0-dev. The current pre-release of v1.15 is v1.15.0-rc2 (0b06b2019) and is 607 commits after v1.15.0-dev.
You'll see that github has highlighted & changed those SHAs into links into our commit tree. 49ad088b8 is not a commit in Gitea and you'll see that because Github has not changed the SHA into a link.
You have some private changes and you are not testing on v1.15.0-rc2 or the latest head of v1.15.0.
You need to explain what those changes are and/or you need to update.
Thanks for your quick reply. I guess that either my git upstream isn't pointed to the right place or the fix isn't in the release/main branch yet. I don't know where to check the head. The version I provided is what I see on the bottom of the home page.
Rebuild a clean version of Gitea.
I suggest you perform a clean checkout: git checkout v1.15.0-RC2
or git checkout release/v1.15
or git checkout main
Ensure that the checkout is clean - removing any old and weird files that you have - git status
would help with that.
49ad088b8 is not a commit in Gitea - if you have changes that you wish to keep you will need to show that those changes are not the cause of your problems and explain why the SHA has changed (at the least with a git diff 49ad088b8 origin/release/v1.15
(v1.15.0-RC2
or main
)) - but realistically we cannot support private patches on this forum.
realistically we cannot support private patches on this forum.
If you'd like to commission a maintainer to review your code changes and support your issue please reach out (there are several maintainers who can offer paid support), otherwise, as @zeripath mentioned, we cannot support private patches.
I will close this issue now.
I try to trust the git code control practice. I learn that this is a proper way to merge my local changes with the upstream. The only change in my local codebase is the front page. That is not any business local changes in my local code. Assuming the upstream is correct in this regard, that would be a problem in git then.
I get the rc3 branch without any changes, that is not merging it with my local customization code today. And I get the same error.
.
[x]
):Description
Create an application for OAuth on Gitea, log in on its OAuth client app will be redirected to log in on Gttea. At this stage, log in on Gitea with the user account which creates the app will result in the same user log in on its client. In other words, the same user log in to both Gitea and its OAuth client. Log in on Gitea with other user accounts will result in the user account which creates the app on its client app. In other words, different user log in on Gitea and its OAuth client. For some reason, Gitea always returns the user account which creates the app as its OAuth client to its OAuth client for user login based on our current test.
...
Screenshots
The followings are logs for two use cases. Gitea is on the port 3000 while OAuth client is on the port 9000.
1) A user signs in on the OAuth client while a user session is available on Gitea
A user signs in on OAuth client app while the user session isn't available on Gitea.