SpotiByeAds icon indicating copy to clipboard operation
SpotiByeAds copied to clipboard

Github Widget

Open jlogancase opened this issue 5 years ago • 6 comments

When using the GitHub configuration widget and editing an existing configuration if I do not re-enter the 'Personal Access Token', the system will re-encrypt the Token leading to Access Denied errors when the GitHub collector runs..

This raises a related question. Why is the Personal Access Token sent back to the user's browser? It is not being de-encrypted and in this UI mode, can't really be used for anything. It is resulting in errors being produced when editing the form if one is not fully aware of the underlying UI processing mechanism. There are other issues I see, that if interested we can discuss off line.

jlogancase avatar Jun 17 '19 19:06 jlogancase

@jlogancase This is a bug we recently found and will work on getting it fixed.

rvema avatar Jun 17 '19 20:06 rvema

@Sbrenthughes - I am having the issue with persisting "401 unauthorized" on the GitHub widget. Running this locally from several Powershell windows for the api and a couple collectors... . I have no errors showing up on the api logs . I have no errors appearing in the GitHub collector window . The collector appears to be running every 5 minutes as I have it setup

image

Overall I am not sure what the 401 is referring to, the collector seems to be working, I see in the GitHub collector window, and I don't see errors occurring in the Mongo database window where errors are occurring there. But after each collector cycle I still see nothing in the Code Repo Widget

image

TonyMorrison avatar Sep 17 '19 17:09 TonyMorrison

hi @TonyMorrison , did you find a solution to this issue?

try adding github.errorThreshold=50 Once the repo errors out a certain amount of time it will not longer try to connect

Sbrenthughes avatar Oct 17 '19 19:10 Sbrenthughes

Any updates? I am experiencing similar situation with Github widget. No error in github/API collector log at all. but I can see the red light on the widget that indicates server 500. It happens when I associated a private repo. A public repo will work fine with same configuration here. Please help me out of there. Thanks in advance.

yangdutw avatar Apr 07 '20 07:04 yangdutw

I'm also having a similar issue - using the config from the collector repo, no issues in the logs, but persistently nothing being collected. Is there a default config that should work for public repos?

samwiskow avatar Dec 08 '20 11:12 samwiskow