Missing python packaging user guide #4576
Comments
|
More Context: Prior to deletion I added my new account, Projects affected:
I feel like I'm forgetting one... |
|
To specify: I deleted the RTD account. I disassociated the old RTD account from my GitHub account before deletion. |
|
The symptoms from my side are the same as those that Thea is seeing on her new account: projects where we're co-maintainers (i.e. including Thea's old account) are not appearing in my project list at https://readthedocs.org/dashboard/ |
|
Ok, I was able to replicate this in my local instance. Looks like we are deleting all projects that belong to a user when it deletes its account (even if this wasn't the original owner of the project). |
|
Yeah I'm thinking that if there are *any* other owners the project
shouldn't be deleted. In this case it was my intention to rotate to my new
account, so if projects created by my old account get deleted that would
have defeated the purpose.
…On Mon, Aug 27, 2018, 7:10 PM Santos Gallegos ***@***.***> wrote:
Ok, I was able to replicate this in my local instance. Looks like we are
deleting all projects that belong to a user when it deletes its account
(even if this wasn't the original owner of the project).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4576 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAPUc5qGXDt6YqNj3WxXrLc4j_Ker9Neks5uVKZ4gaJpZM4WOxZ->
.
|
|
Absolutely. We had a similar theoretical bug that we patched a while back, this is a different but related. Let me see if I can easily restore things from a backup |
|
Thank you! (& Sorry again for breaking stuff)
…On Mon, Aug 27, 2018, 8:08 PM Anthony ***@***.***> wrote:
Absolutely. We had a similar theoretical bug that we patched a while back,
this is a different but related. Let me see if I can easily restore things
from a backup
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4576 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAPUcyjXTGu2kisy4ZQ8ElhmhbcwiO7mks5uVLQegaJpZM4WOxZ->
.
|
|
No worries! Everything is in flux since our migration to Azure, so frankly, it might be faster to just recreate the projects unfortunately. |
|
packaging.python.org and google-auth-library-python had a significant
number of redirects in place that would be practically impossible to
recreate.
…On Mon, Aug 27, 2018, 8:13 PM Anthony ***@***.***> wrote:
No worries!
Everything is in flux since our migration to Azure, so frankly, it might
be faster to just recreate the projects unfortunately.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4576 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAPUc_a63azQ0sZlksUmjLZjhGP7sMDZks5uVLV0gaJpZM4WOxZ->
.
|
|
Files for the projects above have mostly been restored, I'm working on the database restore pieces now. Files aren't accessible by domain name until I get data out from the snapshot and back into our production database. Good news: our new database restore procedure has officially been tested though ✔️ |
|
@theacodes there are also some projects where your old account is the only owner, shall I restore those as well? |
|
Yes, if you can restore those and assign to my new account that would be
awesome.
…On Mon, Aug 27, 2018, 10:22 PM Anthony ***@***.***> wrote:
@theacodes <https://github.com/theacodes> there are also some projects
where your old account is the only owner, shall I restore those as well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4576 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAPUc_Kp_T2zie7QufmWTz8ZaeKUPKGMks5uVNOcgaJpZM4WOxZ->
.
|
|
Sounds good. I'll need verification for the changes on the orphaned projects as per our policy on intervening on project changes -- I'll send some verification emails tomorrow. Things are mostly restored now. I didn't reload builds or build commands, if there is anything important there, let us know and we can manage restoring it. I haven't fully tested building either, but things appear okay. I'll wrap up some of the smaller pieces tomorrow morning. |
|
Cool, so after the verification process my access will be restored to all of those projects? |
|
Okay, I'm not sure if this is related or not, but it appears one of the restored projects is not updating properly. See https://nox.thea.codes/en/stable/ and https://nox.thea.codes/en/latest. These docs are quite old. The most recent two builds for latest and stable were successful and pulled in the correct commits from GitHub, but the HTML itself doesn't seem to be updating. |
|
Oops, I didn't test that I restored things with the correct permissions, so there is probably an issue there. I'll check on that later and follow up on email verification |
|
The Python Packaging User Guide has reverted quite a bit as well - most notably, the new Overview page that was merged in pypa/packaging.python.org@4b5e860 is missing. The currently displayed PyPUG build does include the changes from mid-July to update Continuum Analytics references to Anaconda, Inc (to account for the company name change), so it's likely that that's just the most recently archived version. However, I forced a new build, and even though that reported itself as successful, the https://packaging.python.org doesn't appear to have updated to the latest version. (@theacodes I also added you back as a project maintainer on the user guide) |
|
Yeah I rebuilt nox again earlier today as well and it's still not updating.
…On Thu, Aug 30, 2018, 10:52 AM Nick Coghlan ***@***.***> wrote:
The Python Packaging User Guide has reverted quite a bit as well - most
notably, the new Overview page that was merged in
***@***.***
<pypa/packaging.python.org@4b5e860>
is missing.
The currently displayed PyPUG build *does* include the changes from
mid-July to update Continuum Analytics references to Anaconda, Inc (to
account for the company name change), so it's likely that that's just the
most recently archived version.
However, I forced a new build, and even though that reported itself as
successful, the https://packaging.python.org doesn't appear to have
updated to the latest version.
***@***.*** <https://github.com/theacodes> I also added you back as a
project maintainer on the user guide)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4576 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAPUcw5f0MKCqD4lBEKX536oCTkgQaTRks5uV_w3gaJpZM4WOxZ->
.
|
|
Sorry, we had a busy day yesterday, so i'm just now getting to my yesterday todo list. @theacodes it looks like nox is updating correctly. I see the version of nox that is marked as stable showing up at https://nox.thea.codes/en/stable/. I think latest looks correct too? @ncoghlan I think the pypa guide is also updating correctly. Can you confirm your versions look as you expect, or if they don't, that rebuilding does update the hosted versions as you'd expect? |
|
The overview is back in PyPUG, so it does look like that's building again: https://packaging.python.org/overview/ Potentially still a CDN cache invalidation issue, though? |
Details
This is based on this tweet.
Expected Result
I expect the packaging guide to be there
Actual Result
It is not there
The text was updated successfully, but these errors were encountered: