Approximately 3% of the time, issue fork creation gets a “Exception in initial branch creation for …: 403 Forbidden”

We should handle that exception and not record metadata about the initial branch until it is created, so the UI doesn’t drift from reality. We currently record the metadata early, instead of waiting for the usual webhook, so people see it is (usually) available right away.

Additionally, we could do one retry with a sub-second delay. This smells like we’re doing something before GitLab is ready for it in the new repository. Since it succeeds much of the time, we probably only need to wait.

Comments

drumm created an issue. See original summary.

  • drumm committed 5bc1dbd3 on 7.x-3.x
    Issue #3349480: Delete record of initial branch if there is a problem...
drumm’s picture

Assigned: Unassigned » drumm
Status: Active » Fixed

We now delete Drupal.org’s record of the new branch if it fails, so when you reload the page, its ready to create the branch again.

  • drumm committed 5bc1dbd3 on reg-prot
    Issue #3349480: Delete record of initial branch if there is a problem...

Status: Fixed » Closed (fixed)

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