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

Maximum Call Stack exceeded - 2.3.4 (See Fail to import custom options #5573) #30043

Closed
jasonhall0612 opened this issue Sep 14, 2020 · 2 comments
Labels
Issue: ready for confirmation Reported on 2.3.4 Indicates original Magento version for the Issue report. stale issue

Comments

@jasonhall0612
Copy link

Preconditions (*)

2.3.4
Google Chrome browser Version 85.0.4183.102 (Official Build) (64-bit)
Linux OS
There was bug issue #5573 but that appears to never have been merged into the main branch

Steps to reproduce (*)

  1. Click to add a new configurable product
  2. Expand customizable options
  3. Click on Add Option rapidly to add say ten options
  4. Check dev tools console in browser debugger

Expected result (*)

No console log errors

Actual result (*)

image

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

  • S0 at this point the user has to refresh the browser and lose all the options in order to save the product
@m2-assistant
Copy link

m2-assistant bot commented Sep 14, 2020

Hi @jasonhall0612. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this


⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Sep 14, 2020
@ghost ghost added Issue: ready for confirmation and removed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed labels Oct 20, 2020
@magento-engcom-team magento-engcom-team added the Reported on 2.3.4 Indicates original Magento version for the Issue report. label Nov 13, 2020
@stale
Copy link

stale bot commented Jan 28, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

@stale stale bot added the stale issue label Jan 28, 2021
@stale stale bot closed this as completed Feb 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: ready for confirmation Reported on 2.3.4 Indicates original Magento version for the Issue report. stale issue
Projects
None yet
Development

No branches or pull requests

2 participants