-
-
Notifications
You must be signed in to change notification settings - Fork 754
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
[FEATURE REQUEST] Allow to add our own GitHub token for requests #3154
Comments
No. We won't. This ratelimit is enough unless you reload Spotify every 5 seconds. |
wrong (tried with 2 random extensions) : 2024-09-01_15-21-01.1.mp4 |
This can also happen if you share the same ip address with someone who abuses the github api, or if you're in a really big subnet, which is quite common for those who can't access spotify without a vpn or those on campus. |
Still am not sure how it's related to the cli itself. It would only apply to the update command which you don't really use frequently so this rate limit thingy wont affect you |
indeed it isn't but where tf is the repo with spicetify's actual source code ?
I'd be glad to open the issue in the appropriate repo and even make a PR for this, but god damn it's nowhere to be found.
Last time I checked, ❯❯ C:\Windows\System32
❯ spicetify backup
spicetify v2.38.3
info Spicetify up-to-date
info There is available backup.
info Clear current backup:
warning After clearing backup, Spotify cannot be backed up again.
info Please restore first then backup, run "spicetify restore backup" or re-install Spotify then run "spicetify backup".
❯❯ C:\Windows\System32
❯ spicetify apply
spicetify v2.38.3
info Spicetify up-to-date
Overwriting themed assets:
OK
success Custom CSS is updated
success Theme's JS is updated
Applying additional modifications:
OK
Transferring custom apps:
OK
success Spotify is spiced up!
success Enabled DevTools! also I read your announcement on discord so I definitely understand that this small problem is absolutely not a priority at all |
Normal user won't run |
my bad, I thought that the marketplace repo was only holding responsibility for listing some extensions and themes and wasn't what actually implements spicetify's core functionalities |
I'm sorry? Marketplace doesn't hold any of cli core functionalities. If you want to mitigate 403 http and rate limit errors in marketplace do it in marketplace's repo. |
Hey there, sorry to barge into this convo, but it seemed related to my issue. I must be overlooking things:
*note, ah the error is from github itself. Yeah iknow how to fix auth issues by adding a personal acces token, but the cli doesnt support that as the person pointed out above. Perhaps we could at something about it in the spicetify docs? ----- old oudated comment -----------
Reading this current thread the solution is: Wait? Is spicetify update all what it does git clone the new release somewhere? |
indeed it's github telling you to read their docs |
Is there another way to update Spicetify except for running spicetify update via the cli? |
Any luck with this guys ? |
While i agree that nobody would run So if you have some other program that also uses the Api, its in fact very possible to exceed those 60 times an hour. And very much so if you work in an office enviroment, where everyone shares the same IP adress, Its also how i figured out that even random commands that spicetify does include a fetch for version update...
Why does enabling devtools, trigger a API request? Iknow it would be quite a bit of effort to include a new config option, and then link the value from that to probably here Line 67 in 01f5cc5
but then with req, err := http.NewRequest("GET", assetURL, nil)
if err != nil {
utils.Fatal(err)
}
req.Header.Set("Authorization", "Bearer YOUR_TOKEN")
resp2, err := http.DefaultClient.Do(req)
if err != nil {
utils.Fatal(err)
} and here cli/jsHelper/spicetifyWrapper.js Line 2458 in 01f5cc5
const res = await fetch('https://api.github.com/repos/spicetify/cli/releases/latest', {
headers: {
'Authorization': [${personalAccessToken}],
},
}); |
@WybeBosch that's exactly the point I tried to make but they won't listen... about the requests on every command, in your [Setting]
check_spicetify_update = 0 |
Nobody does, but browsing the Marketplace does when you click on an extension/theme/app to display its description. |
I'm listening. I responded to your request and I disagreed with it. I, not others, me. Regardless if we would want to implement it or not, there's no place to put this token because
Checking extension's README does not count towards the API ratelimit. Marketplace uses |
very true, i share these files too.
or use an env var called
thx for the info ! but i still wonder why it wasn't able to fetch the content and dropped 429's, i don't think i was hitting the 5k limit either... mystery will never be solved |
Sorry if this conversation got a bit heated, this was never my intention, im very happy that people put so much effort and passion in a free tool. I understand why you do not want the headache of adding support for a PersonalAccesToken. It could provide something to read back on for the future, or atleast show that im invested in this topic thats read from the env from wherever the spicetify update command is ran @EDM115 besides creating the PR, i also tried out your solution of intercepting network requests.. just for fun. However.. because i was bored i made that work too aswell. Completely useless of course, but it works and is quite Funny. I thank you both for your time, never meant to offend and i shall leave this topic for what it is and unsubscribe. |
because you're hitting the 429 on the endpoint to manifest. I think it's some stupid thing that fetches manifest when you want to click the readme am sure.
this does not answer my question on how you would want to pass this token to marketplace. we can't read your env from spotify client |
📝 Provide a description of the new feature
We could have a new setting called
github_token
which would take a Github PAT. Even if this token have no rights, it would allow to authenticate on GitHub's API on the behalf of an user.As explained here :
So a new user that just browses the Marketplace, installs apps and applys will hit the limit very easily :
Being authenticated gives us much more freedom :
➕ Additional Information
This would fix reliably #2998 and #1981 (getting 403 errors and "Error parsing Markdown" in-app)
If the setting isn't set or the token is invalid, it would do an unauthenticated call just like it currently does. Else, it would do all GitHub requests authenticated.
Docs would probably need an update for this, maybe in the FAQ.
More overall info here
The text was updated successfully, but these errors were encountered: