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]: error log is not copy-able #32755

Closed
1 task done
rohan-arthur opened this issue Apr 18, 2024 · 1 comment · Fixed by #33263
Closed
1 task done

[Bug]: error log is not copy-able #32755

rohan-arthur opened this issue Apr 18, 2024 · 1 comment · Fixed by #33263
Assignees
Labels
BE Coders Pod Issues related to users writing code to fetch and update data Bug Something isn't working Core Query Execution Issues related to the execution of all queries Debugger Issues related to the debugger FE Coders Pod Issues related to users writing javascript in appsmith High This issue blocks a user from building or impacts a lot of users Integrations Pod Issues related to a specific integration Low effort Takes 1-2 days Needs Triaging Needs attention from maintainers to triage Production QA Pod Issues under the QA Pod QA Needs QA attention Regressed Scenarios that were working before but have now regressed

Comments

@rohan-arthur
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Description

when I have an erroneous query, I see the error both in response and error tabs. In neither of these tabs can I copy the error itself - this is important because I may want to search on google or stackoverflow etc. to rectify the error.

This was working before, so treating this as a regression.

Screen.Recording.2024-04-18.at.10.31.21.mov

Steps To Reproduce

  1. create an erroneous query
  2. execute it
  3. see that there's an error response
  4. try to copy the error --> not able to copy

Public Sample App

No response

Environment

Production

Severity

High (Blocker to building or releasing)

Issue video log

No response

Version

Cloud

@rohan-arthur rohan-arthur added Bug Something isn't working High This issue blocks a user from building or impacts a lot of users Regressed Scenarios that were working before but have now regressed Needs Triaging Needs attention from maintainers to triage Core Query Execution Issues related to the execution of all queries Low effort Takes 1-2 days labels Apr 18, 2024
@rohan-arthur rohan-arthur self-assigned this Apr 18, 2024
@github-actions github-actions bot added the Integrations Pod Issues related to a specific integration label Apr 18, 2024
@wawa79
Copy link

wawa79 commented Apr 23, 2024

Happy to see I am not alone. This is making SQL debuggin terrible with long queries :-)

If it may help, it was working properly in AppSmith version 1.17 and I noticed the issue after upgrading to 1.21.

Running latest version of Chrome Browser.

@Nikhil-Nandagopal Nikhil-Nandagopal added the Debugger Issues related to the debugger label Apr 29, 2024
@github-actions github-actions bot added BE Coders Pod Issues related to users writing code to fetch and update data FE Coders Pod Issues related to users writing javascript in appsmith labels Apr 29, 2024
@sneha122 sneha122 assigned sneha122 and unassigned rohan-arthur and sneha122 Apr 29, 2024
@appsmith-bot appsmith-bot added the QA Needs QA attention label May 13, 2024
@github-actions github-actions bot added the QA Pod Issues under the QA Pod label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BE Coders Pod Issues related to users writing code to fetch and update data Bug Something isn't working Core Query Execution Issues related to the execution of all queries Debugger Issues related to the debugger FE Coders Pod Issues related to users writing javascript in appsmith High This issue blocks a user from building or impacts a lot of users Integrations Pod Issues related to a specific integration Low effort Takes 1-2 days Needs Triaging Needs attention from maintainers to triage Production QA Pod Issues under the QA Pod QA Needs QA attention Regressed Scenarios that were working before but have now regressed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants