Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot view source on Coveralls #1577

Closed
eugirdor opened this issue May 14, 2015 · 9 comments · Fixed by #1603
Closed

Cannot view source on Coveralls #1577

eugirdor opened this issue May 14, 2015 · 9 comments · Fixed by #1603

Comments

@eugirdor
Copy link

When you try and view the source of a file on Coveralls you see the following error instead:

The owner of this repo needs to re-authorize with Github; their OAuth credentials are no
longer valid so the file cannot be pulled from the Github API.

https://coveralls.io/builds/2561958/source?filename=request.js

@simov
Copy link
Member

simov commented May 14, 2015

@nylen can you first Revoke the access to Coveralls from here https://github.com/settings/applications and then login again here https://coveralls.io/ (you might as well delete the coveralls cookies from the Resources tab before that). And this might fix the GitHub status API reporting on the PRs as well.

@simov
Copy link
Member

simov commented May 14, 2015

Actually there might some other issue with coveralls because I'm not seeing the code for my own projects either. Still the above procedure can fix the GitHub's status API at least.

@nylen
Copy link
Member

nylen commented May 17, 2015

It was working fine for me, but I remoked Coveralls access from GitHub. I did not re-add it again, @simov I'll let you do that. One more thing to try later would be to do "delete repo" in Coveralls - I didn't do it because then we would lose all of our build history.

@simov
Copy link
Member

simov commented May 17, 2015

@nylen that's the thing, there is some weird logic in coveralls that you have to be the one initially added the project to be able to delete it, also your login token will be used for calls to the GitHub API, not mine, so without you re-authenticating it won't work.

@nylen
Copy link
Member

nylen commented May 17, 2015

Hmm.. want me to delete the repo from coveralls and see if that helps?

@simov
Copy link
Member

simov commented May 17, 2015

Deleting anything sounds scary, but if that's an option, after that I can try to add it myself.

@nylen
Copy link
Member

nylen commented May 17, 2015

Well.. I tried twice, and got this ClouldFlare 504 message both times:

screen shot 2015-05-17 at 1 43 13 pm

Then, the repo is still up at https://coveralls.io/r/request/request . Looks like there are some things broken with @coveralls.

@simov
Copy link
Member

simov commented Jun 8, 2015

@eugirdor currently we have two coverage badges in our readme - codecov and coveralls Currently coveralls file coverage for request is still broken for some reason, although it magically started to work for my personal projects, but you can see the actual file coverage in codecov. Also the GitHub's status API is finally working (with codecov).

@eugirdor
Copy link
Author

Excellent, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants