Unable to open source files

[nitin-rawat-bci]

I am unable to open source files to actually see branch/lines uncovered in the file.

• Shows page isn't working

[afinetooth]

Hi, @nitin-rawat-bci. If you notice that URL, it's an OAuth related request. Essentially, it means that, at the time, you were not logged into coveralls.io, and that we were trying to log you in via Github OAuth, but it failed.

Can you verify this Github username is your coveralls.io username (that you were using this account to login via Github OAuth)?

Also, can you tell me the resource (the Coveralls Repo URL, or build) you were trying to access at the time?

Thanks.

[shraykay]

Hi, @nitin-rawat-bci. If you notice that URL, it's an OAuth related request. Essentially, it means that, at the time, you were not logged into coveralls.io, and that we were trying to log you in via Github OAuth, but it failed.

Can you verify this Github username is your coveralls.io username (that you were using this account to login via Github OAuth)?

Also, can you tell me the resource (the Coveralls Repo URL, or build) you were trying to access at the time?

Thanks.

@afinetooth I believe I am logged in (and my username matches) and I can access other repos on coveralls in my github organization, but for some reason this link won't work.

When I attempt to visit the above URL, I get redirected to the github app reauthorization page:

[afinetooth]

Hi, @shraykay. This is a new one!

Even when I, who am an admin, click on that link---in fact, even when I try to access this build by itself, without any source file details in url params: https://coveralls.io/builds/49155085

I am also thrown into that Github OAuth reauthorization loop, until it fails with "unusually high number of requests," same as for you and @nitin-rawat-bci.

As I say, I've never seen this before, since I should, as admin, always be able to at least access basic details of any repo, or build page once they exist in our system.

I can't access the repo at its coveralls URL either: https://coveralls.io/github/TriggerMail/trigger_mail

In fact, I am logged out and can't log back in again from that browser window.

The only thing I can think of that would prevent that is IP blocking on the Github org side.

This is born out by our production bug tracking system, which shows this error after the original HTTP request makes an underlying API request to Github:

Caused By: Github::Error::Unauthorized · GET https://api.github.com/repos/TriggerMail/trigger_mail/commits/b95b738c03d5a2b5b53e5456ddd1ea0570f86f08/statuses?access_token=98e5eb3cd79e9fa88887aeaf2d444a3fc1d1c1ce: 401 - Bad credentials See: https://docs.github.com/rest

If you check with your admins and it turns out there is no IP blocking set up for the org, or the repo itself, then there is likely some problem with this commit (which you see in the errored request above): b95b738c03d5a2b5b53e5456ddd1ea0570f86f08

---

Update: FWIW, I don't think my last thought is correct. I just re-tested against another commit and get the same 401 Unauthorized/Bad credentials. New commit: bccfc893c2188c7ef996ee80c0fc349136e3e52c

Caused By: Github::Error::Unauthorized · GET https://api.github.com/repos/TriggerMail/trigger_mail/commits/bccfc893c2188c7ef996ee80c0fc349136e3e52c/statuses?access_token=98e5eb3cd79e9fa88887aeaf2d444a3fc1d1c1ce: 401 - Bad credentials See: https://docs.github.com/rest

I would start at the IP blocking lead first.

[shraykay]

@afinetooth I followed these docs to find out if any ip addresses are blocked, but it seems that we don't have this feature enabled.

see screenshot from our org page:

[afinetooth]

@shraykay and @nitin-rawat-bci, I think the issue here is that the repo in question: https://coveralls.io/github/TriggerMail/trigger_mail

Belongs to a subscription that was cancelled about 6 months ago.

That subscription was created as TriggerMail, which should map directly to a Github org with the same name and capitalization (case matters).

A new subscription, called triggermail, was created around that time, which has a number of active repos, but not that one. That one still seems to be associated with the previous org / subscription.

Happy to share more info on those subscriptions if you like but please email me at support@coveralls.io since some of the information may be sensitive.

If the scenario was just a name change for the same org, you should be able to move the repo to the new org and access it through the new subscription.

[stale[bot]]

This issue has been automatically marked for closure because it has not had recent activity. It will be closed if no further activity occurs. If your issue is still active please add a comment and we’ll review as soon as we can. Thank you for your contributions.