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]: Having a parenthesis in Windows username crashes RedisInsight #2763

Closed
edokan opened this issue Nov 13, 2023 · 3 comments
Closed

[Bug]: Having a parenthesis in Windows username crashes RedisInsight #2763

edokan opened this issue Nov 13, 2023 · 3 comments
Labels
issue Something isn't working

Comments

@edokan
Copy link

edokan commented Nov 13, 2023

Preconditions (Any important steps we need to know)

Steps to reproduce (How to reproduce what you found step by step)

  • Have a username that contains ( in it. The company I support uses Name Surname (Role) format. User profile directory is created by Windows like C:\Users\LongNameSurname(Role, limiting the user name to 20 characters for archaic reasons.
  • Try to run RedisInsight

Actual behavior (A short description of what you found)
Throws an error saying Invalid Regular Expression: Unterminated Group
/C:\Users\LongNameSurname(Role\.redisinsight-v2\logs\redisinsight-errors-2023-11-13.log/

Expected behavior (A short description of what you expected to find)

  • Show main screen

Screenshots (Paste or drag-and-drop a screenshot or a link to a recording)
image

Additional context (Operating system, version of RedisInsight, Redis database version, Redis module version, database type, connection type, logs, or any other information)

  • RedisInsight-v2 v2.36.0.30218
  • Windows 11
@edokan edokan added the issue Something isn't working label Nov 13, 2023
@ViktarStarastsenka
Copy link
Collaborator

@edokan , thank you for reporting this issue.
does the username include any other special characters? Tried with the username pattern you mentioned, and couldn't reproduce the issue

@edokan
Copy link
Author

edokan commented Nov 13, 2023

@ViktarStarastsenka nope. Beside ( no other character. It probably tried to write an error to the log and then this one occurred.

@ViktarStarastsenka
Copy link
Collaborator

@edokan , please try with 2.38 (released today).
re-open the ticket if the issue still reproduces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants