Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Notifier] [Brevo] Handle error responses without a message key#52096

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
nicolas-grekas merged 1 commit intosymfony:6.4fromstof:brevo_error_response
Oct 17, 2023

Conversation

@stof
Copy link
Member

QA
Branch?6.4
Bug fix?yes
New feature?no
Deprecations?no
Tickets
LicenseMIT

During their outage yesterday where the endpoint returned errors with status code 500, there was no message key in the json response.
This avoids a notice when the key does not exist. Instead, it uses the full response content, as done when the decoding fails.

This is the same change than#52095 but for the new Brevo bridge

@carsonbotcarsonbot changed the titleHandle Brevo error responses without a message key[Notifier] Handle Brevo error responses without a message keyOct 17, 2023
@OskarStarkOskarStark changed the title[Notifier] Handle Brevo error responses without a message key[Notifier][Brevo] Handle error responses without a message keyOct 17, 2023
@carsonbotcarsonbot changed the title[Notifier][Brevo] Handle error responses without a message key[Notifier] [Brevo] Handle error responses without a message keyOct 17, 2023
@nicolas-grekas
Copy link
Member

Thank you@stof.

@nicolas-grekasnicolas-grekas merged commitf4b774f intosymfony:6.4Oct 17, 2023
@stofstof deleted the brevo_error_response branchOctober 17, 2023 11:55
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@OskarStarkOskarStarkOskarStark approved these changes

Assignees

No one assigned

Projects

None yet

Milestone

6.4

Development

Successfully merging this pull request may close these issues.

4 participants

@stof@nicolas-grekas@OskarStark@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp