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

GraphQL addProductsToCart mutation reports unrelated errors in user_errors #37908

Closed
1 of 5 tasks
paales opened this issue Aug 22, 2023 · 9 comments · Fixed by #38014
Closed
1 of 5 tasks

GraphQL addProductsToCart mutation reports unrelated errors in user_errors #37908

paales opened this issue Aug 22, 2023 · 9 comments · Fixed by #38014
Assignees
Labels
Area: Product Component: GraphQL GraphQL Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Project: GraphQL Reported on 2.4.6-p2 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@paales
Copy link
Contributor

paales commented Aug 22, 2023

Preconditions and environment

  • 2.4.6-p2
  • Demo products available
  • MSI configured (although not known if it is a specific MSI issue)

Steps to reproduce

  1. Create a product "PRODUCT-1" with inventory of 100

  2. Create a product "PRODUCT-2" with inventory of 100 (make sure indexers etc. have ran)

  3. Create an empty cart:

mutation {
  createEmptyCart(input: {cart_id: "CART_ID_CART_ID_CART_ID_CART_ID_"})
}
  1. Add a product with for quantity of 100 to the cart.
mutation AddProductOne {
  addProductsToCart(cartId: "CART_ID_CART_ID_CART_ID_CART_ID_", cartItems: [{
    sku: "PRODUCT-1",
    quantity: 100
  }]) {
    cart {
      items {
        ... on SimpleCartItem {
          quantity
        }
        errors {
          code
          message
        }
      }
    }
    user_errors {
      code
      message
    }
  }
}
  1. Run this mutation again, you will see an error on user_errors, this is correct.
  2. Change the quantity of PRODUCT-1 to 50 in the backend
  3. Validate that the items[0].errors has entries:
query GetCart {
  cart(cart_id: "CART_ID_CART_ID_CART_ID_CART_ID_") {
    items {
      ... on SimpleCartItem {
        quantity
      }
      product {
        sku
      }
      errors {
        code
        message
      }
    }
  }
}
  1. Add the second product to the cart with quantity of 1
mutation {
  addProductsToCart(cartId: "CART_ID_CART_ID_CART_ID_CART_ID_", cartItems: [{
    sku: "PRODUCT-2",
    quantity: 1
  }]) {
    cart {
      items {
        ... on SimpleCartItem {
          quantity
        }
        product {
          sku
        }
        errors {
          code
          message
        }
      }
    }
    user_errors {
      code
      message
    }
  }
}

Expected result

I would expect the user_errors to be empty because there was no error with the operation, only an error with the cart it's self.

Actual result

user_errors contains the error of the other item..

Additional information

We currently have to do some very dirty checking to see on which item this error occurs and do a string match on the message to filter any cart item errors. This is not foolproof and is slow when there are many items in the cart. This issue arises because add to cart actions become very slow when there are many items in the cart because we fetch those items on each action.

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
@m2-assistant
Copy link

m2-assistant bot commented Aug 22, 2023

Hi @paales. Thank you for your report.
To speed up processing of this issue, 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:


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ 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, join the Community Contributions Triage session to discuss the appropriate ticket.

@m2-assistant
Copy link

m2-assistant bot commented Aug 22, 2023

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.6-p2 Indicates original Magento version for the Issue report. label Aug 22, 2023
@engcom-Bravo
Copy link
Contributor

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

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

@magento-deployment-service
Copy link

@engcom-Bravo
Copy link
Contributor

Hi @paales,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Steps to reproduce

  • Create a product "PRODUCT-1" with inventory of 100
  • Create a product "PRODUCT-2" with inventory of 100 (make sure indexers etc. have ran)
  • Create an empty cart:
mutation {
  createEmptyCart(input: {cart_id: "CART_ID_CART_ID_CART_ID_CART_ID_"})
}
  • Add a product with for quantity of 100 to the cart.
mutation AddProductOne {
  addProductsToCart(cartId: "CART_ID_CART_ID_CART_ID_CART_ID_", cartItems: [{
    sku: "PRODUCT-1",
    quantity: 100
  }]) {
    cart {
      items {
        ... on SimpleCartItem {
          quantity
        }
        errors {
          code
          message
        }
      }
    }
    user_errors {
      code
      message
    }
  }
}
  • Run this mutation again, you will see an error on user_errors, this is correct.
  • Change the quantity of PRODUCT-1 to 50 in the backend
  • Validate that the items[0].errors has entries:
query GetCart {
  cart(cart_id: "CART_ID_CART_ID_CART_ID_CART_ID_") {
    items {
      ... on SimpleCartItem {
        quantity
      }
      product {
        sku
      }
      errors {
        code
        message
      }
    }
  }
}

  • Add the second product to the cart with quantity of 1
mutation {
  addProductsToCart(cartId: "CART_ID_CART_ID_CART_ID_CART_ID_", cartItems: [{
    sku: "PRODUCT-2",
    quantity: 1
  }]) {
    cart {
      items {
        ... on SimpleCartItem {
          quantity
        }
        product {
          sku
        }
        errors {
          code
          message
        }
      }
    }
    user_errors {
      code
      message
    }
  }
}

We have added a PRODUCT-1 with qty 100.

Screenshot 2023-08-23 at 7 34 28 PM

Here We are getting errors it is expected.

Screenshot 2023-08-23 at 7 34 43 PM Screenshot 2023-08-23 at 6 02 34 PM Screenshot 2023-08-23 at 7 40 21 PM

We are getting user errors while adding PRODUCT-2 it is having sufficient stock and quantity there is no issue with this product.There should be no errors still we are getting errors.

Hence Confirming the issue.

Thanks.

@engcom-Bravo engcom-Bravo added Project: GraphQL Area: Product Component: GraphQL GraphQL Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. labels Aug 23, 2023
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-9362 is successfully created for this GitHub issue.

@m2-assistant
Copy link

m2-assistant bot commented Aug 23, 2023

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@Vasudev-22
Copy link
Contributor

@magento I am working on this

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Product Component: GraphQL GraphQL Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Project: GraphQL Reported on 2.4.6-p2 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
4 participants