-
Notifications
You must be signed in to change notification settings - Fork 616
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
Can't publish any more #2617
Comments
Is it possible that the RustAudio org is now more locked down on GitHub? This could be a situation similar to #1368. |
Hmmm indeed. Thanks for the hint! I've granted the crates.io team access for RustAudio and now it works again. It would be nice if it could display warnings if there is no access for it. Can it distinguish between not having access to an organization you are member of and not being a member? |
I don't think we can, at least not with this endpoint alone. As I understand it, we get the same
I think it would be great to extend the existing error message. Do you have more details on exactly what permission change worked for you? I would love to be able link to documentation or at least describe what an org admin needs to check for. I don't have an existing org to poke around the settings myself. |
The weirdest part about this was that you don't have to set it in your organization, but in your personal account. That's what I first struggled with because I didn't find the crates.io oauth app in the RustAudio org settings at all. I had to get to my personal account settings, go to the crates.io oauth app and there's a listing of all organizations I'm member of. I had to authorize the RustAudio org. Basically the same UI that your linked issue has a screenshot of. After I did that, it also worked for the other account rustaudio-publish-bot whose token the CI uses , even though I didn't change anything in there. It just was green all of a sudden. Maybe it's because my personal account is admin in the RustAudio org? IDK. |
Okay, trying to follow along I see the following:
|
Yes! It's the same URL.
Yes. The button was a Grant one though. I think its label depends on whether you are admin or not.
Yeah there is a crates.io entry with a green checkmark and "approved". If I click on the pen it shows me that est31 has requested the approval. I'm not sure about the state before I granted crates.io access. Maybe there were some restrictions, maybe not. There is also an entry in the audit log mentioning that I approved access. |
from the comments here I'm assuming the "Can't publish any more" issue has been solved. if there is anything additional we need to do to prevent such issues in the future I would suggest to open a new issue for that which explains the suggestion :) |
these issues keep coming up in 2022, weird |
@iamgabrielsoft if you are having trouble publishing, please open a new issue with more details. Thanks! |
cpal has a "publish to crates.io" github action in which it tries to publish the crate to crates.io. This has worked great in May at the latest, but now seems to not work any more. The error is:
The publish job uses the Github account @rustaudio-publish-bot which is part of the cpal maintainers team on github. That same team is listed as owner on the crates.io page of cpal: https://crates.io/crates/cpal
This setup used to work but broke for some reason. The token is still valid, it's still shown as "used" recently enough according to the timestamp on crates.io.
I've tried publishing it locally with my own API keys, but it gave the same error for me as well.
See also cpal the bug: RustAudio/cpal#428
And: RustAudio/cpal#337
The text was updated successfully, but these errors were encountered: