Skip to content

Fix typos #68659

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 10, 2024
Merged

Fix typos #68659

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/sentry/issues/escalating_issues_alg.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ def generate_issue_forecast(
is relative to the data. The CV is then placed into an exponential equation that outputs
a multiplier inversely related to how high the cv is. The multiplier is bounded between 2 and 5. The
ceilings for the next week are all the same - which is the maximum number of events in an hour over the
past week multiplied by this multiplier. This calculation is to accound for bursty issues or those that
past week multiplied by this multiplier. This calculation is to account for bursty issues or those that
have a very high variance.
The final spike limit for each hour is set to the max of the bursty limit bound or the calculated limit.
:param data: Dict of Snuba query results - hourly data over past 7 days
Expand Down
2 changes: 1 addition & 1 deletion static/app/utils/replays/hooks/useLogReplayDataLoaded.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ function useLogReplayDataLoaded({fetchError, fetching, projectSlug, replay}: Pro

// BUG(replay): This will often report the discrepancy between errors
// accociated with the replay, and errors the replay knows about.
// ie: When an error is filtered server-side, it would cound as a replay with 1
// ie: When an error is filtered server-side, it would count as a replay with 1
// backend error.
const feErrorIds = replayRecord.error_ids || [];
const beErrorCount = allErrors.filter(
Expand Down
Loading