We have been getting up to one Failed to create wiki exception per day in issue fork creation. Internally in GitLab, this seems to be a timeout. This leaves a GitLab project for the fork, with an empty repository instead of starting the forking process. This leftover project then blocks all future forking of that issue until is is cleaned up.

When this exception is caught we should:

  • Delete the partial fork project
  • Rename it to not collide, deletion happens after a week and the namespace/etc is still used in the meantime
  • Change the path to not collide

Issue fork drupalorg-3192158

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

drumm created an issue. See original summary.

drumm’s picture

drumm
he/him
Location NY, US
commented
Issue summary: View changes

The rate of this happening has decreased, down to one every few days.

drumm’s picture

drumm
he/him
Location NY, US
commented
Assigned: Unassigned » drumm

  • drumm committed 6b02df7 on 7.x-3.x 
    Issue #3192158: Improve exception logging

  • drumm committed ced1e2b on 7.x-3.x 
    Issue #3192158: Also log exception code

drumm opened merge request !35

  • drumm committed 5254205 on 7.x-3.x 
    Issue #3192158: Recover from “Issue fork creation failed!” due to “...
drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

aspilicious changed the visibility of the branch 3192158-recover-failed-wiki to hidden.

aspilicious changed the visibility of the branch 3192158-recover-failed-wiki to active.