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

Remake order functionality non-deterministic behavior #2964

Closed
2 of 5 tasks
Zanuff opened this issue May 27, 2019 · 10 comments
Closed
2 of 5 tasks

Remake order functionality non-deterministic behavior #2964

Zanuff opened this issue May 27, 2019 · 10 comments
Assignees
Labels
3: Medium complexity bug Bug reports P2: Important Priority mark - still high ;) QA approved after merge Testers will add this label after positive check on merged changes QA approved on branch Testers will add this label after positive check on specific branch.

Comments

@Zanuff
Copy link

Zanuff commented May 27, 2019

Current behavior

Remake order functionality ends up with random number of products in cart if not locked on backend side. Probably due to the asynchronicity of the requests.

Expected behavior

Remake order functionality should end up with the same number of products in cart after clicking remake order.

Steps to reproduce the issue

  1. Have an account with orders
  2. Have an order with multiple products added
  3. Go to my orders and click remake order
  4. See how the cart id updated several times and end up with different number of tiems and totals

Can you handle fixing this bug by yourself?

  • YES
  • NO

Which Release Cycle state this refers to? Info for developer.

Pick one option.

  • This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
  • This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
  • This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.
@Zanuff Zanuff added the bug Bug reports label May 27, 2019
@pkarw pkarw added 3: Medium complexity P2: Important Priority mark - still high ;) labels May 27, 2019
pkarw added a commit that referenced this issue May 29, 2019
…inistic cart sync behaviors + refactor to async/await #2964
@pkarw pkarw added the QA - Ready for tests This is notification for testers, that improvement is ready to be tested and verified. label May 29, 2019
@alinadivante
Copy link
Collaborator

Something is wrong when I try remake really big order (94 items).. Look at minicart-counter
big_order

@alinadivante alinadivante removed the QA - Ready for tests This is notification for testers, that improvement is ready to be tested and verified. label May 30, 2019
@pkarw
Copy link
Collaborator

pkarw commented May 30, 2019

Ok, it’s on the branch 2513 right?

@alinadivante
Copy link
Collaborator

Yes @pkarw - feature/2513

@pkarw pkarw added the QA - Ready for tests This is notification for testers, that improvement is ready to be tested and verified. label May 31, 2019
@pkarw
Copy link
Collaborator

pkarw commented May 31, 2019

OK, I've refactored it a little bit #2887

@alinadivante
Copy link
Collaborator

Nice job!

@alinadivante alinadivante added QA approved on branch Testers will add this label after positive check on specific branch. and removed QA - Ready for tests This is notification for testers, that improvement is ready to be tested and verified. labels Jun 4, 2019
@pkarw pkarw closed this as completed Jun 4, 2019
@patzick patzick added the QA - Ready for tests This is notification for testers, that improvement is ready to be tested and verified. label Jun 11, 2019
@alinadivante
Copy link
Collaborator

@pkarw I tested it again, after merging, but now I see a problem with a duplicate notification and it takes a while before the user is redirected to the checkout. See my new video.
big_order

Imho there should be loader displayed or information about the processing.

@alinadivante alinadivante reopened this Jun 12, 2019
@alinadivante alinadivante added QA rejected Testers will add this label when something is still wrong and removed QA - Ready for tests This is notification for testers, that improvement is ready to be tested and verified. labels Jun 12, 2019
@pkarw
Copy link
Collaborator

pkarw commented Jun 12, 2019

OK, we need to add the check for duplicated notification in the core/modules/cart/store/actions.ts:583

@pkarw pkarw self-assigned this Jun 12, 2019
@pkarw
Copy link
Collaborator

pkarw commented Jun 12, 2019

I've also got a console error: vuex.esm.js:410 [vuex] unknown action type: cart/getPaymentMethods

@pkarw
Copy link
Collaborator

pkarw commented Jun 12, 2019

Check also the forceServerSync when entering Checkout.js. Currently it is set with the remake order - and probable shouldn't be (it will save us on cart sync)

@pkarw
Copy link
Collaborator

pkarw commented Jun 12, 2019

Plus as @alinadivante wrote - adding a popup / blocking loader

@pkarw pkarw closed this as completed Jun 18, 2019
@GabiDivante GabiDivante added QA approved after merge Testers will add this label after positive check on merged changes and removed QA rejected Testers will add this label when something is still wrong labels Jun 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3: Medium complexity bug Bug reports P2: Important Priority mark - still high ;) QA approved after merge Testers will add this label after positive check on merged changes QA approved on branch Testers will add this label after positive check on specific branch.
Projects
None yet
Development

No branches or pull requests

5 participants