Skip to content

Conversation

@HazAT
Copy link
Member

@HazAT HazAT commented Feb 28, 2020

Description of why can be found here: getsentry/sentry-javascript#2459

  • Update @sentry/* deps

@HazAT HazAT self-assigned this Feb 28, 2020
@HazAT HazAT merged commit 74785e6 into master Feb 28, 2020
@HazAT HazAT deleted the fix/apm-react-profiler branch February 28, 2020 13:31
description: `<${displayName}>`,
},
{
autoPopAfter: 500, // After this timeout we'll pop this activity regardless
Copy link
Member

Choose a reason for hiding this comment

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

@billyvg would this timeout be sufficient?

Copy link
Member

Choose a reason for hiding this comment

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

@HazAT Does this mean if the react component is waiting for a request that takes longer than 500ms to finish before ending this span, it will automatically pop after 500ms?

Copy link
Member Author

Choose a reason for hiding this comment

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

@billyvg Yes, exactly, so renders now never take longer than 500ms, and the span will be marked with the status Deadline_Exceeded.

One example when this occurred:
Sometimes when you navigation change into the project creation page in Sentry, the render activity was started but never ended, that's how we determined this "bug".
So I know this is not ideal but I had no idea how to debug why sometimes the profiler is not calling finish.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants