Skip to content
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]: Failure to run 'dab init' command because InitOptions could not be initialized successfully #2470

Open
1 task done
kurkoc opened this issue Nov 20, 2024 · 0 comments
Assignees
Labels
bug Something isn't working cri Customer Reported issue triage issues to be triaged

Comments

@kurkoc
Copy link

kurkoc commented Nov 20, 2024

What happened?

Due to a culture related bug in CommanLineParser, I can't run dab init command when dealing with TR culture. Because of the small i, big İ problem in Turkish, the Issuer field can't be parsed.

I forgot to take a screenshot before I changed the computer's culture but I was getting an error saying “Immutable with invalid constructor”. I think this problem has been addressed here

Version

1.2.14+c7ca8db8558a63919c530e454c8f18b45d5b931c

What database are you using?

Azure SQL

What hosting model are you using?

Static Web Apps (SWA)

Which API approach are you accessing DAB through?

REST

Relevant log output


Code of Conduct

  • I agree to follow this project's Code of Conduct
@kurkoc kurkoc added bug Something isn't working triage issues to be triaged labels Nov 20, 2024
@JerryNixon JerryNixon added the cri Customer Reported issue label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cri Customer Reported issue triage issues to be triaged
Projects
None yet
Development

No branches or pull requests

3 participants