-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Unable to access private build status on gitlab #8768
Comments
The GitHub token pool errors are unrelated. I can't see anything obviously wrong with your settings from what you've posted. I think the next thing I would try is: If you SSH into your server, you should be able to run |
So I tried what you said but it seems it tries to relaunch the server which is obviously already running so I get this error:
|
Ah, yes. |
Ok I did it the log is really huge ca not find the problem in it:
|
Right, yes. I see the issue now. You should find all the other gitlab badges (license, issues, releases, contributors, etc) work fine for your private repos but pipeline status and coverage don't - right? The reason why pipeline status and coverage don't work is because they don't get their data from the GitLab API. They are basically "scrapers" for the GitLab native badges which allow them to be re-styled with the shields formatting options. These badges were added a long time ago when GitLab's API rate limits were still really restrictive. Because they don't use the API, they can't pass an auth token. They'll only work for public repos. To solve this, we'll need to rewrite those to get their data from the API like the other GitLab badges. |
Fair enough that's quite clear. Didn't check the other badges. I will wait if one day the other method is implemented. Thanks a lot for your help. |
If anyone wants to pick this up
|
Are you experiencing an issue with...
My own instance of shields
🐞 Description
Hi,
I'm running an instance via Docker on my server which is working perfectly.
But when I want to add a status from a private repo from gitlab I get a inaccessible badge.
Here my setup:
Docker tag: server-2022-12-01
Docker-config service:
shields: image: shieldsio/shields:server-2022-12-01 container_name: Shields environment: - PORT=80 - GITLAB_ORIGINS=https://gitlab.com - GITLAB_TOKEN=glpat-sometokenkeyhere
I checked the token is valid and grant all access (for testing purpose)
At the same time sometimes 8n the logs of Shields docker I got this error:
Shields | 0103155818 Error: Token pool is exhausted Shields | at TokenPool._nextBatch (file:///usr/src/app/core/token-pooling/token-pool.js:268:11) Shields | at TokenPool.next (file:///usr/src/app/core/token-pooling/token-pool.js:305:20) Shields | at GithubApiProvider.tokenForUrl (file:///usr/src/app/services/github/github-api-provider.js:147:33) Shields | at GithubApiProvider.fetch (file:///usr/src/app/services/github/github-api-provider.js:160:22) Shields | at GithubForks._request (file:///usr/src/app/core/base-service/base.js:234:40) Shields | at GithubForks._requestGraphql (file:///usr/src/app/core/base-service/base-graphql.js:74:35) Shields | at GithubForks._requestGraphql (file:///usr/src/app/services/github/github-auth-service.js:66:18) Shields | at GithubForks.handle (file:///usr/src/app/services/github/github-forks.service.js:57:29) Shields | at Function.invoke (file:///usr/src/app/core/base-service/base.js:407:45)
I don't know if it's related.
Thanks in advance.
🔗 Link to the badge
No response
💡 Possible Solution
No response
The text was updated successfully, but these errors were encountered: