-
-
Notifications
You must be signed in to change notification settings - Fork 268
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
Reset token for r-forge #496
Conversation
Copying from cf-staging fails due to "invalid feedstock token". refs: - conda-forge/r-forge-feedstock#8
Thanks for the merge!
|
We are likely out of requests. Retry the workflow later. This workflow uses the same tokens and code as staged recipes. |
We're still running into invalid feedstock token errors. |
Does a retry fix it ? |
I've retried the upload jobs from the master branch already without success. Should I try rerendering as well? |
Rerendering doesn't seem to update anything in this case. |
Which feedstocks? |
Just r-forge that I've seen so far: https://github.com/conda-forge/r-forge-feedstock |
Ah ok. Looks like Travis is still barfing on the token reset. |
I'll have to debug locally but won't get a chance for a while. Is this a big blocker? |
Not a big one, no. It's only blocking a handful of packages in the R 4.2 migration, so it doesn't really matter if this gets addressed today or next week. Thanks! |
Apart from the remaining All workflow runs of https://github.com/conda-forge/admin-requests/actions failed since merging this PR with token registration on Travis not working (see #496 (comment) ). So might be rather specific to https://github.com/conda-forge/r-forge ? (Not sure if relevant/if it helps to pin point the issue: that feedstock also hasn't been built since the CFEP13 token cleanup migration.) |
Travis appears to not have this feedstock on its website - https://app.travis-ci.com/github/conda-forge/r-forge-feedstock IDK why. Maybe we can submit it to staged recipes again to see if that helps? |
Or we could disable Travis here... |
Thanks for looking into it! |
Right ok. We'll have to make a special run of the feedstock token reset code or add that feature. I will try for today. |
Try this again. The token has now been reset. |
Thank you! Just started it and will check in 4-5 hours (afk). |
Seems to have done the trick! |
Copying from cf-staging fails due to "invalid feedstock token".
refs:
cc @conda-forge/r-forge
Guidelines for marking packages as broken:
instead of marking packages as broken. This alternative workflow makes environments more reproducible.
not technically broken and should not be marked as such.
but should be patched in the repo data and be marked unbroken later.
the maintainers only, we can allow packages to be marked broken more liberally.
conda-forge/core
) try to make a decision on these requests within 24 hours.What will happen when a package is marked broken?
broken
label to the package. Themain
label will remain on the package and this is normal.anaconda.org
CDN picks up the new patches, you will no longer be able to install the package from themain
channel.Checklist:
broken/*
for adding thebroken
label,not_broken/*
for removing thebroken
label, ortoken_reset/*
for token resets)