GraphQL Endpoint Error in Developer and Default Modes

[jr-magento-dev]

Preconditions and environment

Summary of the issue

Magento is throwing error when hitting graphql endpoint with introspection query.

Magento Version

Magento Community Edition2.4.6-p3

Steps to reproduce

When sending a GraphQL request to the /graphql endpoint with the following payload:

{
  __schema {
    types {
      kind
      name
      possibleTypes {
        name
      }
    }
  }
}

the following error is encountered in Developer and Default modes:

Error Message: Missing required argument $subject of Magento\SalesGraphQlAux\Model\Resolver\SearchTerm.
File: vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php
Line: 264

Same endpoint and same codebase is giving successful response on production operation mode.

Expected result

The success response on the below should be reachable in all environments, not only in production mode.

{
    "data": {
        "__schema": {
            "types": [
                {
                    "kind": "OBJECT",
                    "name": "Query",
                    "possibleTypes": null
                },
                {
                    "kind": "SCALAR",
                    "name": "ID",
                    "possibleTypes": null
                },
                {
                    "kind": "SCALAR",
                    "name": "Boolean",
                    "possibleTypes": null
                },
                ....
                ....
                ....
                ....
                ....
                {
                    "kind": "OBJECT",
                    "name": "__EnumValue",
                    "possibleTypes": null
                },
                {
                    "kind": "OBJECT",
                    "name": "__Directive",
                    "possibleTypes": null
                },
                {
                    "kind": "ENUM",
                    "name": "__DirectiveLocation",
                    "possibleTypes": null
                }
            ]
        }
    }
}

Actual result

{
    "errors": [
        {
            "message": "Internal server error"
        }
    ]
}

Additional information

Issue only occurs on developer and default modes. Endpoint is working as expected on production mode.

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]

Hi @jr-magento-dev. 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:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

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.

[jr-magento-dev]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @jr-magento-dev. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @jr-magento-dev, here is your Magento Instance: https://2f9f1a6acad8484bd0788e80ac446d07.instances-prod.magento-community.engineering
Admin access: https://2f9f1a6acad8484bd0788e80ac446d07.instances-prod.magento-community.engineering/admin_8040
Login: af821a2a
Password: 580e2baf941e

[m2-assistant]

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]

Hi @jr-magento-dev,

Thank you for reporting and collaboration.

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

Steps to reproduce

When sending a GraphQL request to the /graphql endpoint with the following payload:

{
  __schema {
    types {
      kind
      name
      possibleTypes {
        name
      }
    }
  }
}

We have enabled developer mode and we are not getting any error.

Kindly recheck the issue in Magento 2.4-develop instance and elaborate the steps if the issue is still reproducible.

Thanks.

[olgamchuk]

Hi, having the same issue on Magento CE 2.4.6-p3, error repeats in development mode.

[engcom-Bravo]

Hi @olgamchuk,

Thanks for your update.

We have verified the issue in Latest 2.4-develop instance and the issue is not reproducible.Could you please verify the issue in Latest Magento 2.4-develop instance it might be possible issue got fixed in Magento 2.4-develop instance.

Thanks.

[engcom-Bravo]

Hi @jr-magento-dev,

We have noticed that this issue has not been updated since long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks