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

[Bug] REPO_INDEXER doesn't index mirrored repository, even if the NotifySyncPushCommits is called #11479

Closed
2 of 7 tasks
ghost opened this issue May 18, 2020 · 5 comments
Closed
2 of 7 tasks

Comments

@ghost
Copy link

ghost commented May 18, 2020

  • Gitea version (or commit ref): 1.11.5
  • Git version: Not relevant
  • Operating system: docker image
  • 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: Not relevant

Description

Looks like #11200 wasn't a fix to this bug.

Can we trigger the indexing manually on a selected repository? Or is it possible to call NotifyPushCommits manually form GUI, or via some command-line?

func (r *indexerNotifier) NotifyPushCommits(pusher *models.User, repo *models.Repository, refName, oldCommitID, newCommitID string, commits *repository.PushCommits) {

@zeripath
Copy link
Contributor

Please could you check on master/1.12 if the current fix is sufficient.

Things in the indexer changed quite a between those two.

@techknowlogick
Copy link
Member

Current master can be found here: https://dl.gitea.io/gitea/master/

@ghost
Copy link
Author

ghost commented May 18, 2020

@techknowlogick Thanks!
I have just tried the artifacts, and it seems that the bug persists.
It's a bit strange that it only happens to the mirrored repos, and the indexing of normal repos isn't influenced.

@ghost
Copy link
Author

ghost commented Jun 19, 2020

Any update on this?

@ghost
Copy link
Author

ghost commented Jun 21, 2020

solved

@ghost ghost closed this as completed Jun 21, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants