Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GitLab CI issue

See original GitHub issue

I’ve no idea what happened (hence the vague title) but I will tell you as much as I can.

I was working on a project attached to a private gitlab repo. All has been working fine, no issues like this have cropped up before. I was working on a branch, forms, which I then merged into dev. Forms locally was one commit ahead of forms remotely, and local dev was 2 commits ahead of remote dev (including the merge commit). I then pushed the two commits on my local dev branch to the remote dev branch.

We then have Gitlab CI automatically upload it to our server. This is where the 2 errors appeared.

The interesting thing is that I can’t see which message caused the error - all the messages seemed to come through just fine.

Anyway, here’s the error in text form. Both errors seem the exact same.

An error has occured on skyhook for your webhook with provider gitlab. Maybe you can screenshot this error and open an issue on the skyhook GitHub. Error: "TypeError: Cannot read property 'name' of undefined\n    at GitLab.<anonymous> (/app/dist/providers/GitLab.js:173:92)\n    at Generator.next (<anonymous>)\n    at /app/dist/providers/GitLab.js:6:71\n    at new Promise (<anonymous>)\n    at __awaiter (/app/dist/providers/GitLab.js:2:12)\n    at GitLab.build (/app/dist/providers/GitLab.js:172:16)\n    at GitLab.<anonymous> (/app/dist/model/BaseProvider.js:56:33)\n    at Generator.next (<anonymous>)\n    at fulfilled (/app/dist/model/BaseProvider.js:3:58)\n    at process._tickCallback (internal/process/next_tick.js:68:7)"

Edit: Definitely a CI issue. I cancelled a CI job, and the error appeared again: