Skip to content

fix(remix): Do not capture 4xx codes from thrown responses.#5441

Merged
lobsterkatie merged 1 commit into
masterfrom
onur/remix-avoid-catching-4xx
Jul 21, 2022
Merged

fix(remix): Do not capture 4xx codes from thrown responses.#5441
lobsterkatie merged 1 commit into
masterfrom
onur/remix-avoid-catching-4xx

Conversation

@onurtemizkan
Copy link
Copy Markdown
Contributor

@onurtemizkan onurtemizkan commented Jul 21, 2022

Fixes: #5425

Ref: #5429, #5405

As per review #5429 (comment), we need to define how and when we should capture a 4xx error.

We will only capture thrown 5xx responses until then.

Copy link
Copy Markdown
Member

@lobsterkatie lobsterkatie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lobsterkatie lobsterkatie merged commit 25c3dc7 into master Jul 21, 2022
@lobsterkatie lobsterkatie deleted the onur/remix-avoid-catching-4xx branch July 21, 2022 18:53
@alexblack
Copy link
Copy Markdown

Great to see this merged! Do you know when it might get released?

@eltonchan
Copy link
Copy Markdown

image
I also encountered the same problem, it seems that it should be the same root cause

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Object.captureException

4 participants