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]: The stack trace limit gets exceeded if the data send to the execute call is large #36383

Closed
1 task done
AmanAgarwal041 opened this issue Sep 18, 2024 · 1 comment · Fixed by #36482
Closed
1 task done
Assignees
Labels
Bug Something isn't working Frontend This label marks the issue or pull request to reference client code High This issue blocks a user from building or impacts a lot of users Integrations Product Issues related to a specific integration Needs Triaging Needs attention from maintainers to triage Production QA Pod Issues under the QA Pod QA Needs QA attention Query Forms Isuses related to the query forms Query & JS Pod Issues related to the query & JS Pod

Comments

@AmanAgarwal041
Copy link
Contributor

AmanAgarwal041 commented Sep 18, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Description

When we have an action with large number of data to be passed to the execute action call, it loops to a function updateBlobDataFromUrls which performs some functionality and then stores that value in an array. If the length of the array to be looped is quite large then the stack trace limit gets exceeded which results in no execute call getting fired or anything further.

Steps To Reproduce

  1. Create an api action which takes an object and one of the keys should accept array of strings i.e. { "sids": ["hello", "hello2"] }
  2. Run the query with array items more than 800 strings
  3. Observe the execute calls never goes in and the loader icon gets stuck for a particular timeout

Public Sample App

No response

Environment

Production

Severity

Low (Cosmetic UI issues)

Issue video log

No response

Version

Both

@AmanAgarwal041 AmanAgarwal041 added Bug Something isn't working Needs Triaging Needs attention from maintainers to triage labels Sep 18, 2024
@Nikhil-Nandagopal Nikhil-Nandagopal added Low An issue that is neither critical nor breaks a user flow Production labels Sep 18, 2024
@AmanAgarwal041 AmanAgarwal041 added Query & JS Pod Issues related to the query & JS Pod High This issue blocks a user from building or impacts a lot of users and removed Low An issue that is neither critical nor breaks a user flow labels Sep 18, 2024
@github-actions github-actions bot removed the Query & JS Pod Issues related to the query & JS Pod label Sep 18, 2024
@AmanAgarwal041 AmanAgarwal041 added Frontend This label marks the issue or pull request to reference client code Query Forms Isuses related to the query forms Query & JS Pod Issues related to the query & JS Pod labels Sep 18, 2024
@github-actions github-actions bot added the Integrations Product Issues related to a specific integration label Sep 18, 2024
@AmanAgarwal041 AmanAgarwal041 changed the title [Bug]: The event loop gets blocked if the data send to the execute call is large [Bug]: The stack trace limit gets exceeded if the data send to the execute call is large Sep 23, 2024
@sujdev7
Copy link

sujdev7 commented Sep 23, 2024

Slack thread of discussion here

@appsmith-bot appsmith-bot added the QA Needs QA attention label Oct 9, 2024
@github-actions github-actions bot added the QA Pod Issues under the QA Pod label Oct 9, 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 Frontend This label marks the issue or pull request to reference client code High This issue blocks a user from building or impacts a lot of users Integrations Product Issues related to a specific integration Needs Triaging Needs attention from maintainers to triage Production QA Pod Issues under the QA Pod QA Needs QA attention Query Forms Isuses related to the query forms Query & JS Pod Issues related to the query & JS Pod
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants