-
Notifications
You must be signed in to change notification settings - Fork 67
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
[Bug] infinite loop when excluding all symbols and strictly requiring symbols #48
Comments
The same error happens with the following options: |
I also got
I fixed it by escaping
It seems like any misconfiguration throws this error. |
Thanks:
From: Kingsley Hause ***@***.***>
Sent: Wednesday, March 2, 2022 7:54 PM
To: brendanashworth/generate-password ***@***.***>
Cc: Dániel Némethy ***@***.***>; Comment ***@***.***>
Subject: Re: [brendanashworth/generate-password] [Bug] infinite loop when excluding all symbols and strictly requiring symbols (#48)
I also got Maximum call stack size exceeded with the following configuration:
const symbols = '$*.[]{}()?\\-"!@#%&/\\,><^\':;|_~`+=';
{
length: 32,
lowercase: true,
numbers: true,
strict: true,
symbols,
uppercase: true,
}
I fixed it by escaping ] to be \\] so the full string of symbols will be:
$*.[\\]{}()?\\-"!@#%&/\\,><^\':;|_~\`+=
It seems like any misconfiguration throws this error.
—
Reply to this email directly, view it on GitHub<#48 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADDDYKCVLNLNCQQQQMOHBEDU562LNANCNFSM4OR4AOGQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
generate-password v1.5.1
currently has a bug which results in a max callstack size exceededThe bug occurs when strictly requiring and then excluding those characters.
i.e.
Could we instead throw an error if the configuration is not possible?
The text was updated successfully, but these errors were encountered: