-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
Docs out of date regarding CDN time #1735
Comments
This now typically takes ~2 hrs to sync, so definitely something we should mention in the doc as it's surprisingly slow. |
This week, a change is being pushed that will have the CDN update time at ~8 minutes instead of several hours. Edit: See barabo's comment below for more info. |
Also would want to update this line to reflect that change |
@kathatherine any update on this? 🙂 |
Anyone is welcome to submit this PR and update the FAQ |
Thanks for the reminder, @leofang. I recall there being a bit of a delay on this as some bugs were worked out. If anyone can give me the actual new number, I'm happy to create a PR. |
I can help make the PR, but I was simply curious if there's any reference I can link to 🙂
|
The channel clone job runs every ~2 minutes, and it takes about 6 minutes to complete. So, it's typically about a 10 minute delay from upload in anaconda.org to availability in the CDN. If that's not happening, check the status page: https://conda-forge.org/status/ for the If the clone is not sync'ing - you can open a CDN Issue in the Anaconda Issues repo. I have a |
From our perspective (conda-forge), things have been working smoothly for some time now 🙂 |
Thanks all, I'll update the doc. |
Where should the content be changed?
https://conda-forge.org/docs/maintainer/maintainer_faq.html#mfaq-anaconda-delay
What should be changed?
The FAQ should say that it may take several hours for the CDN to update.
Additional information
See: https://app.element.io/#/room/#conda-forge:matrix.org/$1649163456813vMMND:gitter.im
Incorrect or outdated
The text was updated successfully, but these errors were encountered: