Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • heptapod heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 163
    • Issues 163
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • heptapodheptapod
  • Issues
  • #64

Closed
Open
Created Jul 03, 2019 by Georges Racinet@gracinet🦑Owner

Creation and destruction of project not immediately taken into account

Right after a project has been created, there's an amount of time during which hg clone or any other CLI command will fail with HTTP 404.

The reason is that the running internal hgwebdir (with Gunicorn in our current standard setup) rescans its base directories periodically. The default refresh interval time is 20s. This is slow enough that a human being might notice, and it's a major impediment for our functional tests.

Lowering that interval isn't probably very wise for performance reasons. In principle, the hgwebdir WSGI app should be able to be triggered into refreshing itself via signals or some other dedicated channel.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking