-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Internal Server Error in /V1/products/special-price API Endpoint #35934
Comments
Hi @mlf20. Thank you for your report.
Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
For more details, review the Magento Contributor Assistant documentation. Add a comment to assign the issue: To learn more about issue processing workflow, refer to the Code Contributions.
🕙 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, join the Community Contributions Triage session to discuss the appropriate ticket. ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
Hi @engcom-November. Thank you for working on this issue.
|
@magento give me 2.4-develop instance |
Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-November, here is your Magento Instance: https://334b8526e05c78ff6198b9cb88e71670.instances.magento-community.engineering |
Hi @mlf20 , |
Hi @engcom-November, Thanks for looking at this, I believe the reason you are unable to reproduce this is due to the use of the 'prices' in the reequest body. In my original issue the body of the request malformed, being set to: '{"prices": "\"[]\""}'. Many thanks |
Hi @mlf20 Getting expected result: 400 bad request error on 2.4-develop branch |
Hi @engcom-November, My apologies, I have gone over my logs and the payload in thebody should be '{"prices": "[]"}' . Due to formatting the initial request body had escaped additional characters. I will update the remaining issues. |
@magento give me 2.4-develop instance |
Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-November, here is your Magento Instance: https://334b8526e05c78ff6198b9cb88e71670.instances.magento-community.engineering |
Thanks for the update @mlf20 . Verified the issue on Magento 2.4-develop branch and the issue is reproducible. Hence updating the description and confirming the issue. |
@magento I am working on this |
@magento give me 2.4-develop instance |
Hi @JettyRohanAditya. Thank you for your request. I'm working on Magento instance for you. |
Hi @JettyRohanAditya, here is your Magento Instance: https://334b8526e05c78ff6198b9cb88e71670.instances-prod.magento-community.engineering |
Preconditions and environment
Steps to reproduce
Payload:
{"prices": "[]"}
or
{"prices": ""}
API's effected with above payload:
Expected result
Returns a 400 error as the request is malformed.
Actual result
Returns a 500 status code from a null TypeError .
Additional information
output of var/log/system.log:
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: