Extremely long response time for `/api/cla/get` route

I recently completed the signing experience for a PR. Upon reaching the CLA assistant app, I encountered a blank template view, so I looked in dev tools to see if there was an issue: there was.

Two POST requests to https://cla-assistant.io/api/github/call responded with 401 status.

Somewhat confused, I closed the tab and tried again. Same result the second time. So I began to do a bit of research. Then, after a couple of minutes, I returned to the tab, and I noticed that the template had been filled with content, so I checked the dev tools again and found a new response:

One POST to https://cla-assistant.io/api/cla/get with a 200 status.

I examined more detail and saw that the response took 74095.52799999983 ms, with 74087.4949999999 ms of that being wait time! That’s 1m14s of waiting for a response!

This issue is mainly a report, but I’d like to know if anything configurable by me contributed to the long wait. If needed, I can provide HAR entry objects for each req/res described above (with cookies redacted). Is there a place I can upload them privately (rather than posting them publicly here)?

[Shegox]

Perfect, thanks a lot for sharing the details 👍

From a first look it seems that indeed some internal logic causes the delay, as the GitHub API requests are quite fast:

Comparing that to when I open the page (~4s):

---

I don’t think this is something caused by your configuration, but more a problem on our side. I think I have tomorrow a bit more time to investigate that.

[jsejcksn]

If you have a timestamp and the (x-cloud-trace or so) response header of one of the long requests would be very helpful. … As well as the link to your CLA signing page (https://cla-assistant.io/$ORG/$REPO)

@Shegox As requested:

api-cla-get.har.jsonc

{
  // ...
  "request": {
    "method": "POST",
    "url": "https://cla-assistant.io/api/cla/get",
    "headers": [
      // ...
      {
        "name": "referer",
        "value": "https://cla-assistant.io/denoland/manual?pullRequest=213"
      },
      // ...
    ],
    // ...
  },
  "response": {
    "status": 200,
    "statusText": "",
    "httpVersion": "http/2.0",
    "headers": [
      // ...
      {
        "name": "x-cloud-trace-context",
        "value": "5d6a98595154e18d183079d7223c152d/4369706350128875755;o=1"
      },
      // ...
    ],
    // ...
  },
  "serverIPAddress": "216.239.32.21",
  "startedDateTime": "2022-01-24T14:28:51.298Z",
  "time": 74095.52799999983,
  "timings": {
    "blocked": 3.7069999988564524,
    "dns": -1,
    "ssl": -1,
    "connect": -1,
    "send": 0.25,
    "wait": 74087.4949999999,
    "receive": 4.076000001077773,
    "_blocked_queueing": 2.1189999988564523
  }
}

From my first message:

This issue is mainly a report, but I’d like to know if anything configurable by me contributed to the long wait.

Please advise. Thanks.