You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In cases where email address do not have any alphabets in then to use in the genration of a geni username, this variable statically assigned "geni1" as a prefix.
Later down in the code line 114, the for loop counts to a max of 99 and also imposing a restriction that the len(username) is within 6 characters. Well we hit the limit of "geni199" today after which new users were not being created and GENI Portal/CH responding with errors. We need a better way of generating the username in such cases. For now my patch just replaces "geni1" assignment to "geni2" which is good for another 99 more such cases. Quick and dirty. This has been patched on the production server and a code patch here will follow soon.
The text was updated successfully, but these errors were encountered:
My memory is that because the username is combined with the CH name et al, that full protogeni slice name length limits were a problem, but I could be wrong. (Was it slice name? Something else?)
What are the normal GENI username length limits? Also 6?
Could we replace that 1 or 2, as well as the following 2 characters with and give ourselves 36^3 usernames?
geni-ch/plugins/marm/MAv1Implementation.py
Line 105 in b6626a1
In cases where email address do not have any alphabets in then to use in the genration of a geni username, this variable statically assigned "geni1" as a prefix.
Later down in the code line 114, the for loop counts to a max of 99 and also imposing a restriction that the len(username) is within 6 characters. Well we hit the limit of "geni199" today after which new users were not being created and GENI Portal/CH responding with errors. We need a better way of generating the username in such cases. For now my patch just replaces "geni1" assignment to "geni2" which is good for another 99 more such cases. Quick and dirty. This has been patched on the production server and a code patch here will follow soon.
The text was updated successfully, but these errors were encountered: