-
Notifications
You must be signed in to change notification settings - Fork 56
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
Oops, an error occured #32
Comments
Hi @vorburger, thanks for reporting your issue! So, you've fallen foul of a rule I implemented on gu:who to prevent casual denial-of-service attacks. gu:who requires that your organisation has at least one public member whose account is over 3 months old. At the moment your organisation has zero public members: https://github.com/orgs/TemenosDS/people If you can make even one of your members public, so long as their account is over 3 months old, then gu:who will not blow up. Apologies for the poor way this issue is reported to you, the user. The error message in the logs (updated with #26) is actually quite clear:
I need to fix the user-experience here (gotta pick a scala validation framework!), so will leave this bug open to remind myself. |
Thanks for your prompt response! Sorry to be a pain, but.. are you sure? Because now I'm public on https://github.com/TemenosDS, and retried it, but hit the same red error, logged with IDs 6jbod91gl & 6jbodccak (one Token and one via GitHub). |
I can see you've resolved the public-member problem! Have you setup your 'people' repo? https://github.com/guardian/gu-who/blob/master/people-repo.md |
Oh OK, now it all works... indeed it's a little difficult to guess this from "6jbod91gl" ! ;-) |
Yeah, the feedback to users through the web interface needs to be improved! |
Hello - I've hit a red "Oops, an error occured" with This exception has been logged with id 6jbmp8eo0 & 6jbmpa5ai (tried) twice, if you can fix this it would be great to use this tool.. here's exact steps of what I was doing:
The text was updated successfully, but these errors were encountered: