Status Update
No update yet.
Comments
lu...@gmail.com
Can you provide more details about:
- The name of the repository
- The commit SHA1 and ref you pushed to GerritHub.io
- The GitHub account name that has push permissions to the repository
- The timestamp of the push to GerritHub.io that did not replicate to GitHub
da...@yelhow.com
a) dahersoftware/dfactory
b) f48bce1d72bddcb1bc43aa4107bad90023212a74
c) g33kracc00n / darwiche@yelhow.com
d) Tuesday March 11 at 11:29:28 AM UTC+00:00
Since it wasn't merged automatically, I had to push it to Github repo
manually
Thank you
*Mohamed Darwiche*
Technical Director
<
Discover Alex on
<
On Tue, Mar 4, 2025 at 1:15 PM <buganizer-system@google.com> wrote:
lu...@gmail.com
Hi, You need to look at the GitHub security side as the current OAuth tokens aren't valid anymore the authentication / authorization has failed.
[2025-03-12 11:12:11,495] Cannot replicate to https://github.com/dahersoftware/dfactory.git [CONTEXT pushOneId="15998e31" ]
org.eclipse.jgit.errors.TransportException: https://github.com/dahersoftware/dfactory.git: not authorized
The problem also persists now.
Is the new account authorised to push to the repo? Have you tried importing a brand-new repository and see if that works?
da...@yelhow.com
I revoked the access of OAuth token and then grant access again, same thing.
Yes this github account is allowed to push to the repo and has admin role
too. Actually I'm using it to push manually to the github repo.
Importing a brand-new repo no I didn't, I don't think I understand what do
you mean exactly.
I tried to create a new Gerrit admin account and to import the existing
dahersoftware/dfactory repo, but I had errors saying that I need to delete
the meta/refs first and I couldn't do that either. I did that hoping that
it will generate a new OAuth token.
*Mohamed Darwiche*
Technical Director
<
Discover Alex on
<
On Wed, Mar 12, 2025 at 11:15 AM <buganizer-system@google.com> wrote:
lu...@gmail.com
Importing a brand-new repo no I didn't, I don't think I understand what do you mean exactly.
Create a new repository on your organisation and then logout/login to GerritHub and try import the repository using
I did that hoping that it will generate a new OAuth token.
No, the OAuth management is on GitHub, not Gerrit. See the GitHub settings for OAuth on
da...@yelhow.com
It turned out that the Gerrithub replica was not in sync, because the
organization name changed from dahersoftware to yelhow.
At some point, it was working and the replica was fine, even with different
organization names I'm not sure exactly how.
Solution: I cloned the repo from Github, deleted the refs/meta/config. And
then imported to Gerrithub the repo with the new organization name yelhow.
We will lose the history of comments and reviews but that's fine. The
replica works.
Thank you
*Mohamed Darwiche*
Technical Director
<
Discover Alex on
<
On Wed, Mar 12, 2025 at 2:23 PM <buganizer-system@google.com> wrote:
lu...@gmail.com
I believe I can re-trigger a reindexing of the changes for your newly imported projects and you'll get all the review history back. Can you share with me the list of repositories you'll like to reindex for recovering the reviews?
Luca.
da...@yelhow.com
The only repository we would need to reindex is dahersoftware/dfactory. Our
new repo is yelhow/dfactory.
We really appreciate your support
*Mohamed Darwiche*
Technical Director
<
Discover Alex on
<
On Thu, Mar 20, 2025 at 11:32 AM <buganizer-system@google.com> wrote:
lu...@gmail.com
Did you have only 67 changes?
If I run the show-ref on the repo I see this:
git show-ref | grep changes | grep meta | wc -l
67
Description
I faced that before when a commit was added directly to Github, what broke the replica. And I fixed that by syncing Gerrit And Github.
But now this solution is not working, and the cause is different. The problem was raised when the Github account type was changed by company to organization. And I don't find a place where to restart the connection with the repo.