Problem with Restyler Job #4532593

[kiyarose]

Greetings-

I'm having a problem with a Restyled Job

• Restyled Job: https://restyled.io/gh/dswan36/repos/ezprox/jobs/4532593
• GitHub PR: [ Hotfix ] : Patch for Smart Browsers kiyarose/ezprox#6

What I expected to happen:

Restyle to complete successfully, or to ignore as it cannot make any applicable changes.

What happened instead:

Restyled returns an error after cloning repository

info     Restyler started                owner="dswan36" pull=6 repo="ezprox"
debug    fatal: Couldn't find remote ref pull/6/head
info     Cloning repository             
error    Exception:
callProcess: git "fetch" "--quiet" "--depth" "1" "origin" "pull/6/head:pull-6" (exit 128): failed error={description:"internal error",exitCode:99,severity:"critical",tag:"unknown"}
info     Restyler done                   exitCode=99

Restyled Seems to have tried to possibly pull data that doesn't exist yet? (I'm not sure)
I haven't extensively tested how often this could occur, so I cannot give many details on repro.
This is a friendly notification in case something went wrong, and information can be provided.

Configuration (if applicable):

Configuration is not specified in the repo in question, and therefor is assumed to be default.

[pbrisbin]

Hi there-

Restyled Seems to have tried to possibly pull data that doesn't exist yet? (I'm not sure)

So far this is our best guess at what has happened. GitHub is sending us a webhook of the PR event, but its git systems have not made the PR ref available for cloning yet.

I do not think there is a real fix for this issue, it is just a state that can occur in distributed systems. The only thing we could do is implement some kind of retry-back-off on this particular exception.

Unfortunately, given the infrequency and intermittent-ness of this error, we don't have the bandwidth to work on it at this time. But we are fully open source, and would happily accept a PR in this space. The clone logic kicks off around here.

I've also added a new page on our Wiki. For now, I think this is the best we can do so I'm going to close this Issue. But thank you for reporting.

[kiyarose]

So far this is our best guess at what has happened. GitHub is sending us a webhook of the PR event, but its git systems have not made the PR ref available for cloning yet.

I do not think there is a real fix for this issue, it is just a state that can occur in distributed systems. The only thing we could do is implement some kind of retry-back-off on this particular exception.

Another possible solution, could possibly be to wait X time before trying to pull after the web-hook sends the payload, but given it's not known how inconsistent the ttl for the head can be, that might not be super helpful.

I appreciate your response however, and the wiki page on it.

For now #162 's workaround should most likely also work.
Any solution is tough without resources, but the information is helpful.