This repository has been archived by the owner on Feb 3, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 22
At least one github account doesn't match allowed pattern #194
Labels
Comments
Ah, good catch, thank you! I suspect the panic was probably because the newer regex includes more capture groups that are being referenced later on. Could you provide the text of the panic, for my reference? |
Line number is actually 461, I added the line that prints "src: <nil>"
|
Oh - well, #187 (which isn't yet merged into dep downstream) should have caused this to not panic, but it wouldn't have actually fixed the error. Still, that at least helps us know that the panic isn't in the deducer itself - it's at least returning out an error. |
This was fixed in #201, so this issue can be closed. |
ah thanks, i'm used to auto-closing |
krisnova
pushed a commit
to krisnova/dep
that referenced
this issue
Apr 21, 2017
The current rules for github usernames only allow for alphanumeric characters or single hyphens and they cannot begin or end with a hyphen. In the past however github username rules were less strict and we need to support these (issue sdboyer/gps#194). Using the Google BigQuery public github dataset, I've checked the usernames of all public commits against the currently defined regex in deduce.go. From these results I've concluded that usernames with multiple consecutive hyphens and usernames that end with a hyphen were allowed in the past and do exist. Fortunately these are the only exceptions I've found, there were no usernames that started with a hyphen or contained any other special characters. In addition, this change now also allows one-letter usernames.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I've run into a github repo that doesn't match the naming rules in deduce.go: https://github.com/sean-/seed. I tried reverting to this line: https://github.com/sdboyer/gps/blob/master/deduce.go#L53, but that now produces a panic down the line - removing the requirement that user name ends with [A-Za-z0-9] fixes this example, although I don't know if that's a good enough fix for everyone. Thanks.
The text was updated successfully, but these errors were encountered: