-
Notifications
You must be signed in to change notification settings - Fork 667
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
Query tool does not open when user is not defined #5575
Comments
akshay-joshi
pushed a commit
that referenced
this issue
Nov 28, 2022
…ered with the PostgreSQL service. #5575
@jouve Many thanks for the bug issue and the workaround. I've spent many hours trying to understand this issue. |
yogeshmahajan-1903
added a commit
to yogeshmahajan-1903/pgadmin4
that referenced
this issue
Nov 30, 2022
…ool icon beside connection status.
yogeshmahajan-1903
added a commit
to yogeshmahajan-1903/pgadmin4
that referenced
this issue
Nov 30, 2022
…ool icon beside connection status.
yogeshmahajan-1903
added a commit
to yogeshmahajan-1903/pgadmin4
that referenced
this issue
Nov 30, 2022
…ool icon beside connection status.
akshay-joshi
pushed a commit
that referenced
this issue
Nov 30, 2022
akshay-joshi
pushed a commit
to akshay-joshi/pgadmin4
that referenced
this issue
Dec 1, 2022
…ered with the PostgreSQL service. pgadmin-org#5575
akshay-joshi
pushed a commit
to akshay-joshi/pgadmin4
that referenced
this issue
Dec 1, 2022
akshay-joshi
pushed a commit
to akshay-joshi/pgadmin4
that referenced
this issue
Dec 1, 2022
…ered with the PostgreSQL service. pgadmin-org#5575
akshay-joshi
pushed a commit
to akshay-joshi/pgadmin4
that referenced
this issue
Dec 1, 2022
This is tested on candidate build and is fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
when opening the query tool, I see the following message:
{"success":0,"errormsg":"'NoneType' object has no attribute 'replace'","info":"","result":null,"data":null}
instead of the query tool.how to reproduce:
workaround: add a Username in Connection>Username, the query tool works again
logs:
The text was updated successfully, but these errors were encountered: