docs(replay): Replay Issue types & hydration errors #10686

ryan953 · 2024-07-12T21:49:48Z

This moves some stuff around to make room for a new replay issue type: Hydration errors

Previous Hierarchy:

url	Breadcrumbs	Note
`/product/issues/issue-details/replay-issues/`	"Product Walkthroughs / Issues / Issue Details / Replay Issues"	renamed, see next table

New Hierarchy:

url	Breadcrumbs	Note
`/product/issues/issue-details/replay-issues/`	"Product Walkthroughs / Issues / Issue Details / Replay Issues"	added
`/product/issues/issue-details/replay-issues/rage-clicks/`	"Product Walkthroughs / Issues / Issue Details / Replay Issues / Rage Click Issues"	renamed from above
`/product/issues/issue-details/replay-issues/hydration-error/`	"Product Walkthroughs / Issues / Issue Details / Replay Issues / Hydration Errors"	added
`/platforms/javascript/session-replay/issue-types/`	"Platforms / JavaScript / Set Up Session Replay / Replay Issues"	added

I also moved some FAQ-like content from the old :"... Issue Details / Rage Clicks" page (/product/issues/issue-details/replay-issues/) into the troubleshooting page (/platforms/javascript/session-replay/troubleshooting/).

Fixes getsentry/sentry#74357

vercel · 2024-07-12T21:49:51Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sentry-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 17, 2024 5:42pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
develop-docs	⬜️ Ignored (Inspect)	Visit Preview		Jul 17, 2024 5:42pm

michellewzhang

✨

docs/platforms/javascript/common/session-replay/issue-types.mdx

docs/product/issues/issue-details/replay-issues/index.mdx

docs/product/issues/issue-details/replay-issues/rage-clicks.mdx

docs/platforms/javascript/common/session-replay/issue-types.mdx

docs/platforms/javascript/common/session-replay/troubleshooting.mdx

docs/product/issues/issue-details/replay-issues/rage-clicks.mdx

docs/platforms/javascript/common/session-replay/issue-types.mdx

Co-authored-by: Michelle Zhang <56095982+michellewzhang@users.noreply.github.com> Co-authored-by: Catherine Lee <55311782+c298lee@users.noreply.github.com> Co-authored-by: Salma Alam-Naylor <52798353+whitep4nth3r@users.noreply.github.com>

codecov · 2024-07-16T18:26:57Z

Bundle Report

Changes will increase total bundle size by 1.88kB ⬆️

Bundle name	Size	Change
sentry-docs-server	9.26MB	1.89kB ⬆️
sentry-docs-edge-server	253.55kB	3 bytes ⬇️
sentry-docs-client	7.88MB	6 bytes ⬇️

drguthals

Left some suggested changes

drguthals · 2024-07-16T19:21:11Z

docs/product/issues/issue-details/replay-issues/index.mdx

-5. Choose the action to be performed in the "THEN" dropdown.
-6. Decide how often you'd like Sentry to look for rage click issues.
-7. Lastly, name your alert and add an owner.
+After a replay is accepted, consuming replay quota in the process, error detection takes place and error events are grouped into issues, but without consuming issue quota. These errors are created on the backend after ingest and they will not appear on your [Stats](https://sentry.io/orgredirect/organizations/:orgslug/stats/) page under the "Total Errors" or "Accepted Errors" graphs. You are not billed for their volume.


The first sentence here doesn't make sense to me. Am I just missing something?

I think the most confusing is the word "accepted", do you mean created? Do our users have to accept something to make a replay actually show up? Who/what is doing the accepting and where and when?

Also, when you say issue quota, do you mean error quota? Just looking at our docs and I don't see "issue quota" https://docs.sentry.io/pricing/quotas/

Maybe instead:
When a replay is created it consumes replay quota (not to be confused with error quota). After it is created, Sentry checks for errors and any error events associated with the replay are grouped into issues; note that this does not consume issue quota. These errors are created on the backend after ingest and they will not appear on your stats page under the "Total Errors" or "Accepted Errors" graphs. You are not billed for their volume.

drguthals · 2024-07-16T19:22:20Z

docs/product/issues/issue-details/replay-issues/rage-clicks.mdx

+
+If you've enabled [Session Replay](/product/explore/session-replay/), you'll be able to see rage click issues on the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues/) page in Sentry. Rage clicks are a series of consecutive clicks on the same unresponsive page element. They are a strong signal of user frustration and most likely deserve your attention.
+
+![Rage click issue](./img/Rage-click-issue-in-issue-stream.png)


Should we take this moment to update this image to an Empower Plant one to avoid having copyright content on the docs?

docs/product/issues/issue-details/replay-issues/rage-clicks.mdx

docs/product/issues/issue-details/replay-issues/hydration-error.mdx

drguthals · 2024-07-16T19:29:11Z

docs/product/issues/issue-details/replay-issues/hydration-error.mdx

+
+The image slider tool allows for comparing the two page states by overlaying the images on top of each other. Click and drag the purple line to reveal one image or the other.
+
+![image slider tool](./img/hydration-error-image-slider-tool.png)


This and the next images are so tiny it's really hard to even tell what they are showing. Can we make them a bit more zoomed in?

This one the marketing team is going to help followup and make an Arcade or video. A flat image is the worst; people need to see it moving.

Oh awesome :D

docs/product/issues/issue-details/replay-issues/hydration-error.mdx

docs/platforms/javascript/common/session-replay/issue-types.mdx

billyvg · 2024-07-16T20:15:31Z

docs/platforms/javascript/common/session-replay/issue-types.mdx

+
+"Slow clicks" (also called "dead clicks") are only detected on `<button>`, `<input>`, and `<a>` elements that don't lead to updates to the DOM or a page scroll within 7 seconds. When the user clicks on one of these elements 3 or more times within that 7 second time frame, it indicates frustration, and the SDK registers a ["rage click"](/product/issues/issue-details/replay-issues/rage-clicks/).
+
+Sometimes rage or dead clicks will be detected on elements which are not expected to mutate the DOM, like a "Print" or "Download" button. In this case, you can configure `slowClickIgnoreSelectors`, which will prevent those buttons from generating new issues. See <PlatformLink to="/session-replay/troubleshooting/#why-am-i-seeing-too-many-or-too-few-rage-clicks">Why am I seeing too many or too few rage clicks?</PlatformLink> for more.


for more what?

remove that extra link. the slowClickIgnoreSelectors tip is all that we have everywhere.

docs/platforms/javascript/common/session-replay/issue-types.mdx

docs/product/issues/issue-details/replay-issues/hydration-error.mdx

docs/platforms/javascript/common/session-replay/issue-types.mdx

Co-authored-by: Billy Vong <billyvg@users.noreply.github.com> Co-authored-by: Sarah Guthals <sarah@guthals.com>

…ugh i stay on the dev server

…680073038

…679958686

Chatted in slack, good to go and iterate along the way!

jas-kas · 2024-07-17T21:39:27Z

docs/product/issues/issue-details/replay-issues/index.mdx


 <Note>
-While you can enable **session replay** with JavaScript SDK version 7.27.0, or higher, you'll need to have version 7.60.1 or higher in order to be able to see **rage click issues**.
+Replay issues do not consume issue quota.


Suggested change

Replay issues do not consume issue quota.

Replay issues do not consume error quota.

Issues don't have a quota allotment, errors do!

jas-kas · 2024-07-17T21:40:20Z

docs/product/issues/issue-details/replay-issues/index.mdx

-5. Choose the action to be performed in the "THEN" dropdown.
-6. Decide how often you'd like Sentry to look for rage click issues.
-7. Lastly, name your alert and add an owner.
+When a replay is created it consumes [replay quota](/pricing/quotas/manage-replay-quota/) (not to be confused with [error quota](/pricing/quotas/manage-event-stream-guide/)). As the replay session is being processed by the server Sentry detects the replay issue types listed below and groups those into issues. These errors are created on the backend after ingest and do not comsume error quota. They will not appear on your [stats](https://sentry.io/orgredirect/organizations/:orgslug/stats/) page under the "Total Errors" or "Accepted Errors" graphs. You are not billed for their volume.


Suggested change

When a replay is created it consumes [replay quota](/pricing/quotas/manage-replay-quota/) (not to be confused with [error quota](/pricing/quotas/manage-event-stream-guide/)). As the replay session is being processed by the server Sentry detects the replay issue types listed below and groups those into issues. These errors are created on the backend after ingest and do not comsume error quota. They will not appear on your [stats](https://sentry.io/orgredirect/organizations/:orgslug/stats/) page under the "Total Errors" or "Accepted Errors" graphs. You are not billed for their volume.

When a replay is created it consumes [replay quota](/pricing/quotas/manage-replay-quota/) (not to be confused with [error quota](/pricing/quotas/manage-event-stream-guide/)). As the replay is being processed by the server, Sentry detects the replay issue types listed below and groups those into issues. These errors are created on the backend after ingest and do not consume error quota. They will not appear on your [stats](https://sentry.io/orgredirect/organizations/:orgslug/stats/) page under the "Total Errors" or "Accepted Errors" graphs. You are not billed for their volume.

@ryan953 Can we start with a high-level one-two sentences on what kind of issues are replay issues? 'replay issue' is a Sentry-introduced concept so it will be helpful to provide clarity on what kind of problems they highlight in the first few sentences as a summary (I know you have them individually listed below but I think an overarching statement is helpful)

jas-kas · 2024-07-17T21:44:56Z

docs/product/issues/issue-details/replay-issues/index.mdx

+- [Rage clicks](/product/issues/issue-details/replay-issues/rage-clicks/) are a series of consecutive clicks on the same unresponsive page element. They are a strong signal of user frustration and most likely deserve your attention.

-![Turning off rage click issues](./img/Turning-off-rage-clicks-toggle.png)
+- [Hydration errors](/product/issues/issue-details/replay-issues/hydration-error/) are a React-specific problem that happen when the initial UI does not match what was rendered on the server. They can result in extra work for the browser, and a slower pageload experience for users.


what does 'extra work for the browser' mean here? what extra work?

is the extra work is what's causing the slower pageload experience? if so, we should tie that together in this sentence

jas-kas · 2024-07-17T22:01:28Z

docs/product/issues/issue-details/replay-issues/hydration-error.mdx

+---
+title: Hydration Error
+sidebar_order: 50
+description: "Learn about hydration errors."


Suggested change

description: "Learn about hydration errors."

description: "Learn about Session Replay hydration errors."

to match the description on https://docs.sentry.io/product/issues/issue-details/replay-issues/

jas-kas · 2024-07-17T22:02:32Z

docs/product/issues/issue-details/replay-issues/hydration-error.mdx

+
+## Prerequisites for Seeing Hydration Error Diff Tools
+
+Hydration Errors can come into your issue stream either as regular error events, or they could be detected inside a replay session and converted into an issue by the server. Read more about


Suggested change

Hydration Errors can come into your issue stream either as regular error events, or they could be detected inside a replay session and converted into an issue by the server. Read more about

Hydration Errors can come into your issue stream either as regular error events, or they could be detected inside a replay and converted into an issue by the server. Read more about

This is really confusing :/ Can we clarify that hydration errors from 'regular error events' are filtered out via inbound filters

The linked page [configuring hydration errors](/platforms/javascript/session-replay/issue-types/) does talk about the inbound filters and what the different preference options are, i think it's ok to only have that in one spot. Also, it is confusing!

jas-kas · 2024-07-17T22:22:26Z

docs/product/issues/issue-details/replay-issues/hydration-error.mdx

+
+## Privacy
+
+The diff tools all rely on replay data, so any PII data within the webpage will be masked or blocked before being sent to the server. Read more about [Protecting user privacy in Session Replay](/security-legal-pii/scrubbing/protecting-user-privacy/) and [how to configure Session Replay to maintain user privacy](/platforms/javascript/session-replay/privacy/).


Suggested change

The diff tools all rely on replay data, so any PII data within the webpage will be masked or blocked before being sent to the server. Read more about [Protecting user privacy in Session Replay](/security-legal-pii/scrubbing/protecting-user-privacy/) and [how to configure Session Replay to maintain user privacy](/platforms/javascript/session-replay/privacy/).

The diff tools all rely on replay data, so any PII data within the webpage will be masked or blocked before being sent to the server by default. Read more about [Protecting user privacy in Session Replay](/security-legal-pii/scrubbing/protecting-user-privacy/) and [how to configure Session Replay to maintain user privacy](/platforms/javascript/session-replay/privacy/).

jas-kas · 2024-07-17T22:23:58Z

docs/platforms/javascript/common/session-replay/issue-types.mdx

+
+A _[replay issue](/product/issues/issue-details/replay-issues/)_ is an issue detected using captured Session Replay data. If your application is configured with [Session Replay](/product/session-replay/), problems will be detected on the server side during replay ingest, and grouped into issues. We group similar events into issues based on a fingerprint. For replay issues, a fingerprint is primarily based on the problem type and the url or transaction name where the problem occurred.
+
+You can configure which issue types are created by visiting Project Settings > Replay and toggling detection on or off for each issue type.


should we mention that by default this is turned on? so no additional config steps needed

jas-kas · 2024-07-17T22:24:50Z

docs/platforms/javascript/common/session-replay/issue-types.mdx

+
+## Configuring Hydration Errors
+
+When a [hydration error](/product/issues/issue-details/replay-issues/hydration-error/) occurs in your React app, the SDK will emit an error object as well as a replay breadcrumb, both of which contain data about the hydration problem. Both of these are sent to the server for processing. When you're looking at the issue stream you'll see Hydration Error issues which could come from either data source. However you will only see the diff tools which make debugging easier if a replay is associated with the error.


Suggested change

When a [hydration error](/product/issues/issue-details/replay-issues/hydration-error/) occurs in your React app, the SDK will emit an error object as well as a replay breadcrumb, both of which contain data about the hydration problem. Both of these are sent to the server for processing. When you're looking at the issue stream you'll see Hydration Error issues which could come from either data source. However you will only see the diff tools which make debugging easier if a replay is associated with the error.

When a [hydration error](/product/issues/issue-details/replay-issues/hydration-error/) occurs in your React app, the SDK will emit an error object as well as a replay breadcrumb, both of which contain data about the hydration problem. Both of these are sent to the server for processing. When you're looking at the issue stream you'll see Hydration Error issues which could come from either data source. However, you will only see the diff tools which make debugging easier if a replay is associated with the error.

jas-kas · 2024-07-17T22:26:30Z

docs/platforms/javascript/common/session-replay/issue-types.mdx

+
+For this reason we recommend having both [Inbound Filter](/concepts/data-management/filtering/) enabled and the "Create Hydration Error Issues" Replay setting enabled as well. This is also the default!
+
+You can have your preferences configured in one of four ways:


i would just say 'replay' data, instead of replay breadcrumb

jas-kas · 2024-07-17T22:27:25Z

docs/platforms/javascript/common/session-replay/issue-types.mdx

+
+![Replay settings page](./img/replay-settings.png)
+
+## Configuring Rage Click Issues


theres a min SDK version to create rage click issues. this is important for set up. lets mention it here?

ryan953 · 2024-07-17T23:00:55Z

@jas-kas I think I was able to handle all your comments in #10770, but because i'm alt-tabbing a bit more if i missed something we can get to it in another round!

docs(replay): Replay Issue types & hydration errors

a760ce4

all the content

04ae77e

vercel bot had a problem deploying to Preview – sentry-docs July 15, 2024 21:33 Failure

vercel bot had a problem deploying to Preview – develop-docs July 15, 2024 21:33 Failure

ryan953 marked this pull request as ready for review July 15, 2024 21:33

ryan953 requested review from a team and drguthals July 15, 2024 21:35

michellewzhang reviewed Jul 15, 2024

View reviewed changes

michellewzhang requested a review from a team July 15, 2024 22:02

ryan953 requested review from nikolovlazar and whitep4nth3r July 15, 2024 23:50

whitep4nth3r reviewed Jul 16, 2024

View reviewed changes

docs/platforms/javascript/common/session-replay/issue-types.mdx Outdated Show resolved Hide resolved

whitep4nth3r reviewed Jul 16, 2024

View reviewed changes

docs/platforms/javascript/common/session-replay/troubleshooting.mdx Outdated Show resolved Hide resolved

whitep4nth3r reviewed Jul 16, 2024

View reviewed changes

docs/product/issues/issue-details/replay-issues/rage-clicks.mdx Outdated Show resolved Hide resolved

c298lee reviewed Jul 16, 2024

View reviewed changes

docs/platforms/javascript/common/session-replay/issue-types.mdx Outdated Show resolved Hide resolved

Apply suggestions from code review

e6bfd5e

Co-authored-by: Michelle Zhang <56095982+michellewzhang@users.noreply.github.com> Co-authored-by: Catherine Lee <55311782+c298lee@users.noreply.github.com> Co-authored-by: Salma Alam-Naylor <52798353+whitep4nth3r@users.noreply.github.com>

vercel bot had a problem deploying to Preview – develop-docs July 16, 2024 17:30 Failure

vercel bot had a problem deploying to Preview – sentry-docs July 16, 2024 17:30 Failure

convert steps to list

be848b4

vercel bot had a problem deploying to Preview – sentry-docs July 16, 2024 17:40 Failure

vercel bot had a problem deploying to Preview – develop-docs July 16, 2024 17:40 Failure

c298lee approved these changes Jul 16, 2024

View reviewed changes

link to /stats

4576812

vercel bot had a problem deploying to Preview – sentry-docs July 16, 2024 17:52 Failure

vercel bot had a problem deploying to Preview – develop-docs July 16, 2024 17:52 Failure

Merge branch 'master' into ryan953/replay-issue-hydration

8d61ed7

vercel bot deployed to Preview – develop-docs July 16, 2024 18:27 View deployment

vercel bot deployed to Preview – sentry-docs July 16, 2024 18:38 View deployment

drguthals previously requested changes Jul 16, 2024

View reviewed changes

billyvg reviewed Jul 16, 2024

View reviewed changes

bruno-garcia reviewed Jul 16, 2024

View reviewed changes

docs/platforms/javascript/common/session-replay/issue-types.mdx Outdated Show resolved Hide resolved

jas-kas self-requested a review July 17, 2024 11:01

ryan953 and others added 7 commits July 17, 2024 09:42

Apply suggestions from code review

4543aa6

Co-authored-by: Billy Vong <billyvg@users.noreply.github.com> Co-authored-by: Sarah Guthals <sarah@guthals.com>

update copy to mention Dead Clicks before Slow clicks

3385555

Remove domain on links, theyre relative which means when i click thro…

20f8625

…ugh i stay on the dev server

remove extra link with weak CTA

154027b

address https://github.com/getsentry/sentry-docs/pull/10686/files\#r1…

af237ed

…680073038

address https://github.com/getsentry/sentry-docs/pull/10686/files\#r1…

f2fc674

…679958686

update images

9b770d9

ryan953 requested a review from drguthals July 17, 2024 17:27

vercel bot deployed to Preview – sentry-docs July 17, 2024 17:42 View deployment

ryan953 merged commit 16d2e3f into master Jul 17, 2024

ryan953 deleted the ryan953/replay-issue-hydration branch July 17, 2024 22:11

jas-kas reviewed Jul 17, 2024

View reviewed changes

ryan953 mentioned this pull request Jul 17, 2024

docs(replay): Fix typos and more in Replay Hydration Error docs #10770

Merged

github-actions bot locked and limited conversation to collaborators Aug 2, 2024


		If you've enabled [Session Replay](/product/explore/session-replay/), you'll be able to see rage click issues on the [Issues](https://sentry.io/orgredirect/organizations/:orgslug/issues/) page in Sentry. Rage clicks are a series of consecutive clicks on the same unresponsive page element. They are a strong signal of user frustration and most likely deserve your attention.

		![Rage click issue](./img/Rage-click-issue-in-issue-stream.png)


		The image slider tool allows for comparing the two page states by overlaying the images on top of each other. Click and drag the purple line to reveal one image or the other.

		![image slider tool](./img/hydration-error-image-slider-tool.png)


		"Slow clicks" (also called "dead clicks") are only detected on `<button>`, `<input>`, and `<a>` elements that don't lead to updates to the DOM or a page scroll within 7 seconds. When the user clicks on one of these elements 3 or more times within that 7 second time frame, it indicates frustration, and the SDK registers a ["rage click"](/product/issues/issue-details/replay-issues/rage-clicks/).

		Sometimes rage or dead clicks will be detected on elements which are not expected to mutate the DOM, like a "Print" or "Download" button. In this case, you can configure `slowClickIgnoreSelectors`, which will prevent those buttons from generating new issues. See <PlatformLink to="/session-replay/troubleshooting/#why-am-i-seeing-too-many-or-too-few-rage-clicks">Why am I seeing too many or too few rage clicks?</PlatformLink> for more.

	Replay issues do not consume issue quota.
	Replay issues do not consume error quota.

	description: "Learn about hydration errors."
	description: "Learn about Session Replay hydration errors."


		## Prerequisites for Seeing Hydration Error Diff Tools

		Hydration Errors can come into your issue stream either as regular error events, or they could be detected inside a replay session and converted into an issue by the server. Read more about


		## Privacy

		The diff tools all rely on replay data, so any PII data within the webpage will be masked or blocked before being sent to the server. Read more about [Protecting user privacy in Session Replay](/security-legal-pii/scrubbing/protecting-user-privacy/) and [how to configure Session Replay to maintain user privacy](/platforms/javascript/session-replay/privacy/).


		A _[replay issue](/product/issues/issue-details/replay-issues/)_ is an issue detected using captured Session Replay data. If your application is configured with [Session Replay](/product/session-replay/), problems will be detected on the server side during replay ingest, and grouped into issues. We group similar events into issues based on a fingerprint. For replay issues, a fingerprint is primarily based on the problem type and the url or transaction name where the problem occurred.

		You can configure which issue types are created by visiting Project Settings > Replay and toggling detection on or off for each issue type.


		## Configuring Hydration Errors

		When a [hydration error](/product/issues/issue-details/replay-issues/hydration-error/) occurs in your React app, the SDK will emit an error object as well as a replay breadcrumb, both of which contain data about the hydration problem. Both of these are sent to the server for processing. When you're looking at the issue stream you'll see Hydration Error issues which could come from either data source. However you will only see the diff tools which make debugging easier if a replay is associated with the error.


		For this reason we recommend having both [Inbound Filter](/concepts/data-management/filtering/) enabled and the "Create Hydration Error Issues" Replay setting enabled as well. This is also the default!

		You can have your preferences configured in one of four ways:


		![Replay settings page](./img/replay-settings.png)

		## Configuring Rage Click Issues

Uh oh!

docs(replay): Replay Issue types & hydration errors #10686

docs(replay): Replay Issue types & hydration errors #10686

Uh oh!

Conversation

ryan953 commented Jul 12, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vercel bot commented Jul 12, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

michellewzhang left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

codecov bot commented Jul 16, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Bundle Report

Uh oh!

drguthals left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ryan953 commented Jul 12, 2024 •

edited

Loading

vercel bot commented Jul 12, 2024 •

edited

Loading

codecov bot commented Jul 16, 2024 •

edited

Loading