Call to undefined method GuzzleHttp\Exception\ConnectException::getResponse()

[sashas777]

Preconditions and environment

• Magento version 2.4.7-p3
• Install module magento/commerce-eventing
• Connect to App Builder using instructions: https://developer.adobe.com/commerce/extensibility/starter-kit/create-integration/

Steps to reproduce

Before the step: Subscribe to events in Adobe Commerce
Before running the command: npm run commerce-event-subscribe

Add an exception to the Model/IOEventsApi/ApiRequestExecutor.php, Example:

 try {
            $response = $client->request($method, $uri, $params);

            throw new \GuzzleHttp\Exception\ConnectException();

        } catch (GuzzleException $exception) {
            $response = $this->responseFactory->create([
                'status' => $exception->getCode(),
                'reason' => sprintf(
                    'Unsuccessful request: `%s %s` resulted in a `%s %s` response:',
                    $method,
                    $uri,
                    $exception->getResponse()->getStatusCode(),
                    $exception->getResponse()->getReasonPhrase()
                ) . PHP_EOL . $exception->getResponse()->getBody()->getContents()
            ]);
        }

Run npm run commerce-event-subscribe OR bin/magento events:subscribe --fields=sku observer.catalog_product_delete_commit_ater

With a valid exception (when the server response is 403/500/404) There will be an error:

Call to undefined method GuzzleHttp\Exception\ConnectException::getResponse()

In my case, instead of adding an exception, I blocked in the firewall URL https://api.adobe.io/ and it triggered the error.

Expected result

Successful event subscriptions

Actual result

Call to undefined method GuzzleHttp\Exception\ConnectException::getResponse()

Additional information

No response

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 @sashas777. 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.

• 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.

[m2-assistant]

Hi @engcom-Hotel. 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

  - 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-Hotel]

Hello @sashas777,

Thanks for the report and collaboration!

We are discussing this issue internally, till the time moving this issue On Hold.

Thanks

[oshmyheliuk]

Hello @sashas777 ,
Thanks for creating this issue. The fix is already merged and it will be delivered in module-adobe-io-events:1.8.1

[engcom-Hotel]

Thanks @oshmyheliuk for the updates.

As the issue has been fixed and will be delivered in module-adobe-io-events:1.8.1, hence we are closing this issue

Thanks again @sashas777

[sashas777]

@oshmyheliuk

Thank you!