-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
500 Error when opening Collaboration pane #193
Comments
Could someone provide a log? |
The log shows this when going to that page:
|
So right, there is no user 5667.
So looks like we are not deleting the user from collaboration somewhere. @mondele Was this user maybe deleted through the old DW door43.org? We then need to delete from this table too I guess when deleted. |
@mondele You can open that page now. I deleted the bad user from the collaboration table. I'll put a fix into the DW delete user SQL to make sure they are deleted here too. |
Added |
I don't know if this information is still needed, but the user is Chapel Presson. |
@mondele Do you know how he got deleted? |
Unfortunately, no. I could ask Chapel if you like.
John Wood
john_wood@wycliffeassociates.org<mailto:john_wood@wycliffeassociates.org>
[cid:6BA4AD1D-02BF-4D07-85FC-1537323F007B@cyclops.homelinux.net]
Help Desk Supervisor
@jwood on #slack
archistratus on
[cid:AA1E8E39-BD58-48C2-AF4E-8899A3ED28D8@cyclops.homelinux.net]
On Jun 6, 2017, at 10:02 PM, Richard Mahn <notifications@github.com<mailto:notifications@github.com>> wrote:
@mondele<https://github.com/mondele> Do you know how he got deleted?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#193 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AYSeiPx6FfbQm_GKnDQlMRhg_9Uf3Gsuks5sBgS1gaJpZM4Nx2Os>.
|
I get a 500 error when opening the collaboration pane for my repository. https://git.door43.org/Door43/en_uhg/settings/collaboration
It may be that this is related to the deleted groups bug.
The text was updated successfully, but these errors were encountered: