search

lemurheavy / coveralls-public

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

Unable to access private repositories #1728

Closed brookslyrette closed 10 months ago

brookslyrette commented 10 months ago

Since 2023-08-22 we can not access our private repositories. We can list them, and refresh the list but when clicking on the details for a given project we get this error:

Screenshot 2023-08-24 at 10 32 22 AM

Clicking Enable Private Repo Access reloads the page with the same error message.

afinetooth commented 10 months ago

@brookslyrette Quick question: This public issues board is for free / public / open-source subscriptions, which don't have private repos.

If you have private repos that indicates you're a customer from a paid subscription.

In that case, you can get priority support through support@coveralls.io.

Can you share the (paid) subscription and repo your example comes from?

Again, if private or sensitive please email us at support@coveralls.io. You can just reference this issue for background.

tjchambers commented 10 months ago

I also have same problem and got no response from support@coveralls.io. Please suggest an alternative.

brookslyrette commented 10 months ago

Same. I emailed support over 24 hours ago

On Thu, Aug 24, 2023 at 10:56 AM Tim Chambers @.***> wrote:

I also have same problem and got no response from @.*** Please suggest an alternative.

— Reply to this email directly, view it on GitHub https://github.com/lemurheavy/coveralls-public/issues/1728#issuecomment-1691842821, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOLIDBEDFEL6OT3VYY3RWLXW5TRXANCNFSM6AAAAAA35EDS6Q . You are receiving this because you were mentioned.Message ID: @.***>

mrexox commented 10 months ago

Thank you for reporting this issue. Could you please check if your repos are accessible now? We had an issue with access to private repos but now it must be resolved.

tjchambers commented 10 months ago

Works for me now. Please explain why response took So long.

brookslyrette commented 10 months ago

Working now, thanks for fixing

afinetooth commented 10 months ago

@brookslyrette and @tjchambers just want to apologize on behalf of Support here. We've been working through a larger than normal backlog of requests here and are simply behind, which is why we had not yet responded to your email requests. I'm sorry this affected you. We've reached out to both of you individually.