search

lemurheavy / coveralls-public

The public issue tracker for coveralls.io
http://coveralls.io
124 stars 7 forks source link

Opening source files coverage returns 500 in private repo #1637

Open theogf opened 2 years ago

theogf commented 2 years ago

Hi,

I am trying to upload a coverage report for Julia code. The display of coverage percentage works and is correct. But when clicking on file sources, I get a 500 error page. The repo in question is in Gitlab and is private.

I tried the exact same process with a public repo and things are working properly.

This might be related to #886 but the error page is completely different.

afinetooth commented 2 years ago

Hi @theogf. I'll need the Coveralls Repo URL (or project name) to help you with this. I tried to guess, but it looks like you're running a number of projects and the couple I checked seem to be showing source just fine.

If it's sensitive, feel free to email me at support@coveralls.io. You can mention this issue and I'll get it.

dmarin commented 2 years ago

We are hitting this same issue

theogf commented 2 years ago

Hi @theogf. I'll need the Coveralls Repo URL (or project name) to help you with this. I tried to guess, but it looks like you're running a number of projects and the couple I checked seem to be showing source just fine.

If it's sensitive, feel free to email me at support@coveralls.io. You can mention this issue and I'll get it.

I just sent you a mail!

afinetooth commented 2 years ago

@theogf thanks! I'll reply there.

@dmarin are you also on Gitlab?

dmarin commented 2 years ago

yes, we are also on gitlab

afinetooth commented 2 years ago

Ok, @dmarin, I'll reply here if I think this is affecting Gitlab generally.

afinetooth commented 2 years ago

Also, @dmarin — I replied to your email request.

afinetooth commented 2 years ago

General update: It looks like in both cases here there was an issue with the user's Gitlab API token.

Normally, those would not expire, but in one of the cases here, and another case of a Gitlab user with the same issue, UNLINKING the user's Gitlab account from their ACCOUNT page and logging back in fixed the problem.

I suspect the same action will work for the third case as well.

afinetooth commented 2 years ago

Update: Looks like this is a breaking change in Gitlab 15.0:

GitLab.com is moving to 15.0 with a few breaking changes

GitLab no longer supports OAuth tokens without an expiration.

Gitlab Docs: Expiring access tokens

The ability to opt-out of expiring access tokens was deprecated in GitLab 14.3 and removed in 15.0. All existing integrations must be updated to support access token refresh.

I've added a priority issue card to our backlog about this and will post updates here.

dmarin commented 2 years ago

any news about this?

afinetooth commented 2 years ago

Hi, @dmarin. not at this time, sorry to say. I have pinged the card, which will get it a look, and I'll follow up with our developers on Mon.

If you want to check in via email, you can refer to the issue number: 1233.