Why I am seeing this error "No repositories found" for my project https://cgit.drupalcode.org/parallax_blur_bg . Also same for this one https://cgit.drupalcode.org/sandbox-ankitjain28may-2950194.

When/how to clear the cache for your new project

  • Wait 60 minutes. Go ahead and push commits in the meantime, they will be pushed regardless of cgit showing them. cgit’s list of projects is updated hourly.
  • Push a commit, branch, tag, etc. Caches are cleared after a push.

Comments

dbjpanda created an issue. See original summary.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented
Assigned: Unassigned » Mixologic

These pages were cached. I purged the caches for these projects, and those pages are now updated. Your Git pushes all went through well.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented
Title: No repositories found » Improve cgit caching
Project: Drupal.org infrastructure » Drupal.org customizations
Version: » 7.x-3.x-dev
Component: Git » Code

We need

  • Support for purging sandboxes.
  • Something to handle fresh projects. Maybe logic to never cache a "No repositories found" page, or only cache for maybe 15 minutes.
dbjpanda’s picture

dbjpanda CreditAttribution: dbjpanda commented

Yes it solves. Thank you. But the commits for the project parallax_blur_bg and the project name itself is not showing on my profile https://www.drupal.org/u/dbjpanda .

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

You did not properly configure your email address in your git client:

parallax_blur_bg$ git log
commit 5ab07d30874fa940fcdb370d5b3b71da902c76b9 (HEAD -> 8.x-1.x, origin/master, origin/HEAD, origin/8.x-1.x)
Author: Dibyajyoti Panda <dibyajyoti@Dibyajyotis-MacBook-Air.local>

Please follow the instructions at https://www.drupal.org/node/1022156 before pushing new commits. Once you push a commit with a proper email address, it will show up.

  • 7008bac committed on 2950539-proper-sandbox-purges 
    Issue #2950539: Creates a proper surrogate key for sandbox purging

  • 7008bac committed on 2950539-proper-sandbox-purges 
    Issue #2950539: Creates a proper surrogate key for sandbox purging

  • 7008bac committed on 2950539-proper-sandbox-purges 
    Issue #2950539: Creates a proper surrogate key for sandbox purging

  • 0a43516 committed on 7.x-3.x 
    Issue #2950539: Creates a proper surrogate key for sandbox purging

  • 7008bac committed on 2950539-proper-sandbox-purges 
    Issue #2950539: Creates a proper surrogate key for sandbox purging

  • 7008bac committed on 2950539-proper-sandbox-purges 
    Issue #2950539: Creates a proper surrogate key for sandbox purging
Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
CreditAttribution: Mixologic at Drupal Association commented
Status: Active » Needs work

Still need to test/handle fresh repositories.

dbjpanda’s picture

dbjpanda CreditAttribution: dbjpanda commented

Still facing the issue for this repo https://cgit.drupalcode.org/feeds_advance_crawler

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
CreditAttribution: Mixologic at Drupal Association commented

Purged feeds_advance_crawler

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

An extra issue for our current cgit repository viewer is that cgit’s repository list is cached, so even with commits, purging won’t be effective until cgit knows about the new repository.

Regardless of cgit or GitLab, we might need to send a purge request just after repository creation. Or not cache 404s.

Kwadz’s picture

Kwadz CreditAttribution: Kwadz commented

Facing the issue for this repo: https://cgit.drupalcode.org/sandbox-Kwadz-3005315/
Would you be able to purge it?

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented
Issue summary: View changes

Added notes to the issue summary for what to do as a maintainer. This cache is clearable by maintainers, when you push something over an hour after you’ve created the project.

Since it has been well over an hour, https://cgit.drupalcode.org/sandbox-Kwadz-3005315/ looks like it is there.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented
Status: Needs work » Closed (outdated)

This will not be reproducible with GitLab, since the front-end is complex enough to not be able to be cached the same way.