Skip to content

Issue #13952 - Duplicate orders with same Quote Id at same time with few time difference. #35139

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

Closed

Conversation

fiko
Copy link
Contributor

@fiko fiko commented Feb 25, 2022

Description (*)

Two different orders have been placed with very few seconds as time difference with same quote Id.

Fixed Issues (if relevant)

  1. Fixes Duplicate orders with same Quote Id at same time with few time difference. #13952

Manual testing scenarios (*)

  1. Login as a User
  2. Add items to cart and proceed through checkout.
  3. Select Any payment method. Not click on place order button
  4. Now login to the same account in another system.
  5. And proceed to checkout with the same items. Not click on place order button.
  6. Now you have to click on place order at the same time with both the systems.
  7. one of the screen must return failed
    image

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

Resolved issues:

  1. resolves [Issue] Issue #13952 - Duplicate orders with same Quote Id at same time with few time difference. #35833: Issue Duplicate orders with same Quote Id at same time with few time difference. #13952 - Duplicate orders with same Quote Id at same time with few time difference.

@m2-assistant
Copy link

m2-assistant bot commented Feb 25, 2022

Hi @fiko. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests 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 Pull Requests 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

@fiko
Copy link
Contributor Author

fiko commented Feb 25, 2022

@magento give me test instance

@magento-deployment-service
Copy link

Hi @fiko. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

@fiko
Copy link
Contributor Author

fiko commented Mar 3, 2022

@magento run Database Compare, Static Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@fiko
Copy link
Contributor Author

fiko commented Mar 3, 2022

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@fiko
Copy link
Contributor Author

fiko commented Mar 4, 2022

@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@sdzhepa sdzhepa added the Priority: P3 May be fixed according to the position in the backlog. label Mar 10, 2022
@fiko fiko force-pushed the bug/multiple-sales-order-same-quote-id branch from 73048f6 to 7fcd915 Compare May 16, 2022 13:05
@fiko
Copy link
Contributor Author

fiko commented May 16, 2022

@magento run Integration Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@fiko fiko force-pushed the bug/multiple-sales-order-same-quote-id branch from 7fcd915 to d46683c Compare July 24, 2022 08:08
@amine-y
Copy link
Member

amine-y commented Jul 27, 2022

@ihor-sviziev
Why this ticket is not being taken seriously,
The problem is still happening in active Magento installations

@ihor-sviziev
Copy link
Contributor

ihor-sviziev commented Jul 27, 2022

@sidolov @sdzhepa, could you take a look, and reply?

@sdzhepa
Copy link
Contributor

sdzhepa commented Jul 27, 2022

Hello @amine-y and @ihor-sviziev

Thank you for raising this issue!

I do not know the reason but looks like this PR was missed because the related issue was closed: #13952

The issue has a huge thread of comments as I can see a patch was provided to fix it: #13952 (comment).
But the overall situation is not clear is it actual for the current 2.4-develop

@engcom-Alfa and @engcom-Charlie Could you please work together to investigate this problem?
Please review in detail the discussion/comments in #13952
Try to reproduce this issue by the steps from this PR.
Try to check if the patch fixes the issue
If the problem still exists please create and confirm the new issue with all required details. Also please link a new issue with this PR and add all other links to comments if required

Depending on the result please process the PR accordingly
cc: @sidolov

@sdzhepa sdzhepa removed the Priority: P3 May be fixed according to the position in the backlog. label Jul 27, 2022
@ihor-sviziev ihor-sviziev removed the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Jul 28, 2022
Copy link
Contributor

@ihor-sviziev ihor-sviziev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @fiko,
Please review and fix the test failures.

@fiko
Copy link
Contributor Author

fiko commented Aug 7, 2022

@magento run Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@fiko
Copy link
Contributor Author

fiko commented Aug 7, 2022

@magento run WebAPI Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@fiko
Copy link
Contributor Author

fiko commented Aug 7, 2022

@magento run Unit Tests

will try to check, investigate & fix them next week, last week Unit Test was failed, but it's just succeed.

@fiko fiko force-pushed the bug/multiple-sales-order-same-quote-id branch from 684b82b to ded2809 Compare August 12, 2022 07:39
@fiko fiko force-pushed the bug/multiple-sales-order-same-quote-id branch from ded2809 to a5de753 Compare August 12, 2022 07:40
@fiko
Copy link
Contributor Author

fiko commented Aug 12, 2022

@magento run WebAPI Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ihor-sviziev ihor-sviziev removed their assignment Aug 22, 2022
@m2-community-project m2-community-project bot added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Aug 31, 2022
@amine-y
Copy link
Member

amine-y commented Oct 4, 2022

@magento give me test instance

@magento-deployment-service
Copy link

Hi @amine-y. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

@nishant04412
Copy link
Contributor

nishant04412 commented Oct 13, 2022

Hi @fiko and @ihor-sviziev,

This issue has been taken care in internal JIRA ticket. Once Internal PR will get merged, we will notify it here.

JIRA Ref: https://jira.corp.adobe.com/browse/AC-6057

Thank you!

@Denisof
Copy link

Denisof commented Oct 14, 2022

Hi @fiko and @ihor-sviziev, The fix is not correct, in case of any quote errors $this->submitQuoteValidator->validateQuote($quote); a user loses active quote.

@nishant04412
Copy link
Contributor

Hello,

The issue got fixed in the scope of the internal Jira ticket AC-6057 by the internal team
Related commits: https://github.com/magento/magento2/search?q=AC-6057&type=commits

Based on the Jira ticket, the target version is 2.4.6.

Thanks

@engcom-Charlie
Copy link
Contributor

Based on above comment, closing this PR.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Quote Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Release Line: 2.4 Severity: S1 Affects critical data or functionality and forces users to employ a workaround.
Projects
None yet
9 participants