chore: update sample/scripts/update-rn.sh to v0.71.8

chore: update scripts/update-javascript.sh to 7.54.0

Bumps scripts/update-javascript.sh from 7.53.1 to 7.54.0.

Auto-generated by a dependency updater.

Changelog

7.54.0

Important Changes

• feat(core): Add default entries to ignoreTransactions for Healthchecks #8191

  All SDKs now filter out health check transactions by default. These are transactions where the transaction name matches typical API health check calls, such as /^.*healthy.*$/ or /^. *heartbeat.*$/. Take a look at this list to learn which regexes we currently use to match transaction names. We believe that these transactions do not provide value in most cases and we want to save you some of your quota by filtering them out by default. These filters are implemented as default values for the top level ignoreTransactions option.

  You can disable this filtering by manually specifiying the InboundFilters integration and setting the disableTransactionDefaults option:

  Sentry.init({
    //...
    integrations: [new InboundFilters({ disableTransactionDefaults: true })],
  })
  

• feat(replay): Add mutationBreadcrumbLimit and mutationLimit to Replay Options (#8228)

  The previously experimental options mutationBreadcumbLimit and mutationLimit have been promoted to regular Replay integration options.

  A high number of DOM mutations (in a single event loop) can cause performance regressions in end-users' browsers. Use mutationBreadcrumbLimit to send a breadcrumb along with your recording if the mutation limit was reached. Use mutationLimit to stop recording if the mutation limit was reached.

• feat(sveltekit): Add source maps support for Vercel (lambda) (#8256)

  • feat(sveltekit): Auto-detect SvelteKit adapters (#8193)

  The SvelteKit SDK can now be used if you deploy your SvelteKit app to Vercel. By default, the SDK's Vite plugin will detect the used adapter and adjust the source map uploading config as necessary. If you want to override the default adapter detection, you can specify the adapter option in the sentrySvelteKit options:

  // vite.config.js
  export default defineConfig({
    plugins: [
      sentrySvelteKit({
        adapter: 'vercel',
      }),
      sveltekit(),
    ],
  });
  

  Currently, the Vite plugin will configure itself correctly for sveltejs/adapter-auto, sveltejs/adapter-vercel and sveltejs/adapter-node.

  Important: The SvelteKit SDK is not yet compatible with Vercel's edge runtime. It will only work for lambda functions.

Other Changes

• feat(replay): Throttle breadcrumbs to max 300/5s (#8086)
• feat(sveltekit): Add option to control handling of unknown server routes (#8201)
• fix(node): Strip query and fragment from request URLs without route parameters (#8213)
• fix(remix): Don't log missing parameters warning on server-side. (#8269)
• fix(remix): Pass loadContext through wrapped document request function (#8268)
• fix(replay): Guard against missing key (#8246)
• fix(sveltekit): Avoid capturing redirects and 4xx Http errors in request Handlers (#8215)
• fix(sveltekit): Bump magicast to support satisfied keyword (#8254)
• fix(wasm): Avoid throwing an error when WASM modules are loaded from blobs (#8263)

#skip-changelog

Auto-generated by create-pull-request

test: add triggers to build/test for changes in xcodeproj (#3078)

I noticed that https://github.com/getsentry/sentry-cocoa/pull/3071 didn't run build or test checks, which probably should've happened. We didn't actually configure those checks to run those on a project config change.

#skip-changelog

chore: update to Unity 2021.3.26f1 (#1351)

chore: update modules/sentry-java to 6.21.0

Merge branch 'master' into cmanallen/issues-add-replay-issue

Merge branch 'cmanallen/issues-add-replay-issue' into cmanallen/replays-add-slow-click-detector

feat(starfish): update span group breakdown, use metrics (#50086)

This PR updates span group breakdown to use prod data but something funky going on with the data returned by the top n query, bug fix here https://github.com/getsentry/sentry/pull/50105

doesn't implement the updated UI yet

fix(perf-issues): have N+1 detector consider overlapping db spans (#50079)

This change was validated using the Extended N+1 detector (which only records metrics), where we saw an increase of about 8% for N+1s detected.

Remove the check for whether spans overlap, and moev the new _is_slower_than_threshold implementation from the Extended detector to the main detector. Update the N+1 detector tests to confirm that overlapping spans are detected, and remove the duplicated test_n_plus_one_overlapping_db_span_detector.py test file.

feat(starfish): truncate sql query (#50097)

Truncates the query in the db module, the queries were becoming quite long to view

styles(profiling): Align the buttons in span profile details (#50107)

Using baseline means the buttons are misaligned here. Switching to center.

Screenshots

Before

After

feat(span-clusterer): Bump lifetime rules (#50043)

Bump the lifetime of rules that have been applied to span descriptions. Stale rules aren't applied, nor rules that didn't exist before.

feat(starfish): use time spent instead of app impact (#50095)

A couple changes here.

1. Use time spent instead of app impact throughout starfish
2. Add a time spent tooltip explanation
3. Add typing for the table headers.
4. Update some typing to match what they should be based on the query
5. Remove some duplicated types.

feat(functions): Global suspect functions card (#49860)

This introduces a new card to show suspect functions scoped to a project rather than a transaction.

fix(Slack): fix bug resolving in next release (#50126)

This PR fixes a bug where we can't resolve a an issue in the next commit. Resolves https://github.com/getsentry/sentry/issues/50116

fix(functions): Profile functions dataset small fixes (#49919)

Fix type on function duration and ensure is_application is treated as a boolean field.

fix(profiling): draw selected state after grid (#50156)

Fixes https://sentry.slack.com/archives/C02MYEFL2Q7/p1685559790668349

feat(starfish): add p95 to duration charts, use shared title (#50101)

Three main changes are made here

1. Adds p95 to all duration charts in module -> span sample flow
2. Adds a shared colour variable for p95/p50 line graph colours (colours were inconsistent, sometimes p50 was yellow, sometimes orange, etc)
3. Adds a shared titles for duration (Sometimes we just wrote 'Duration', sometimes, we wrote 'Duration (P50)')

fix(sentry-apps): pass org (#50170)

Seems like this was a bug caused from some refactoring of the organization store

fix(proj-creation): Change default team name to 'team-[parsed-email]' (#50123)

Previously, the default team name was default-team-[username]. This had to problem of including the default 32 letter string as the username if the user never changed their sentry username. We instead parse the email username (everything before the @) and use team-[email_username] for shortness and clarity, eg: team-seiji.chew

fix(escalating): Update archive/resolve tooltip copy (#50168)

fixes #50159

fix(query-subscription-consumer): Fix multi processing usage in prod (#50175)

I forgot to pass this boolean through to the subscription consumer. Also adding tags around metrics to differentiate consumers based on group id

feat(dashboard-widget-description-frontend): Added functionality and … (#50162)

Linked Issue: https://github.com/getsentry/sentry/issues/34420

1. Added description textarea in widget builder:

2. Added description to widget previews:

3.Added description to widget viewer modal:

4. Added tests.

Co-authored-by: Abdullah Khan abdullahkhan@PG9Y57YDXQ.local

fix(escalating): Update issue details archive guide copy (#50176)

fix(sort): apply greatest to v2 aggregate_event_score to avoid multiplying by 0 (#50132)

Fixes the scoring so we don't multiply the scores if the aggregate_event_score is 0. Also refactors this function to avoid dupe line.

fix(sort): special aggregation for sorted issue platform issues (#50129)

Workaround to 'support' betterPriority sort for issue platform backed issues.

This basically sets Performance and Profiling issue scores to zero so they end up at the very last in issue search sort order.

Resolves SENTRY-11SS

Revert "fix(query-subscription-consumer): Fix multi processing usage in prod (#50175)"

This reverts commit 3d3e7935946a2b7e7bb5cf397ce3765bcb98a4e4.

Co-authored-by: wedamija 6288560+wedamija@users.noreply.github.com

I also didn't make any front-end changes lol

Just to clarify I did not request reviews from all of these teams...

Environment

How do you use Sentry? sentry.io

Which version of the SDK? 1.4.0

How did you install the package? Git UPM

Which version of Unity?

2022.3.0f1

Is this happening in Unity (editor) or on a player like Android, iOS, Windows?

Android Build

Steps to Reproduce

Add sentry to a new project in 2022.3.0f1, press build

Expected Result

It builds the apk without errors

Actual Result

It builds the apk but with an error

[Error] Error building Player: Sentry: (Error) Failed to modify the 'build.gradle' files. UnityEditor.Build.BuildFailedException: Failed to find scope 'repositories'. at Sentry.Unity.Editor.Android.GradleSetup.InsertIntoScope (System.String gradleContent, System.String scope, System.String insertion) [0x00119] in /sentry-unity/src/Sentry.Unity.Editor/Android/GradleSetup.cs:106 at Sentry.Unity.Editor.Android.GradleSetup.UpdateGradleProject () [0x00022] in /sentry-unity/src/Sentry.Unity.Editor/Android/GradleSetup.cs:32 at Sentry.Unity.Editor.Android.AndroidManifestConfiguration.SetupGradle (System.String gradleProjectPath) [0x0002c] in /sentry-unity/src/Sentry.Unity.Editor/Android/AndroidManifestConfiguration.cs:263 [Error] Sentry: (Error) Failed to modify the 'build.gradle' files. UnityEditor.Build.BuildFailedException: Failed to find scope 'repositories'. at Sentry.Unity.Editor.Android.GradleSetup.InsertIntoScope (System.String gradleContent, System.String scope, System.String insertion) [0x00119] in /sentry-unity/src/Sentry.Unity.Editor/Android/GradleSetup.cs:106 at Sentry.Unity.Editor.Android.GradleSetup.UpdateGradleProject () [0x00022] in /sentry-unity/src/Sentry.Unity.Editor/Android/GradleSetup.cs:32 at Sentry.Unity.Editor.Android.AndroidManifestConfiguration.SetupGradle (System.String gradleProjectPath) [0x0002c] in /sentry-unity/src/Sentry.Unity.Editor/Android/AndroidManifestConfiguration.cs:263

gh pr checkout 55

Environment

pnpm version: 7.29.1 node version: 16.15.1 npm version: 8.11.0

Steps to Reproduce

1. pnpm install
2. @sentry/cli: Running install script, failed

Expected/Actual Result

Error: Command failed \node_modules.pnpm@sentry+cli@1.75.2\node_modules@sentry\cli\sentry-cli.exe --version

Logs

Issue Description

Hello! In working recently with sentry-ruby, a colleague and I found that the recently added global event processors from https://github.com/getsentry/sentry-ruby/issues/1974 don't seem to clear on invocation of Sentry.init. This is a bit unexpected, considering the overall action of Sentry.init to reset other options.

If this is the intended behavior and simply could use a documentation note, then please feel free to close this issue report.

Reproduction Steps

1. Sentry.init to get started
2. Sentry.add_global_event_processor
3. Sentry.init to reset state
4. Sentry.add_global_event_processor
5. Examine Sentry::Scope.global_event_processors.length or similar

For example:

Gemfile

# frozen_string_literal: true

source 'https://rubygems.org'

gem 'rspec'
gem 'rubocop'
gem 'sentry-ruby', '~> 5.9'

spec/sentry_ruby_spec.rb

# frozen_string_literal: true

require 'rspec'
require 'sentry-ruby'

describe Sentry do
  it 'flushes global event processors on .init' do
    # Setup - init and set one global event processor
    Sentry.init
    Sentry.add_global_event_processor do |event, _hint|
      event.tags = { foo: 42 }
      event
    end
    expect(Sentry::Scope.global_event_processors.length).to eq(1)

    # When - init and set another global event processor
    Sentry.init
    Sentry.add_global_event_processor do |event, _hint|
      event.tags = { foo: 42 }
      event
    end

    # Then there should be one global event processor.
    expect(Sentry::Scope.global_event_processors.length).to eq(1)
    # However, this fails: length is 2, because Sentry.init retains global event processors.
  end
end

Expected Behavior

Sentry::Scope.global_event_processors.length shows one configured global event processor.

Actual Behavior

Sentry::Scope.global_event_processors.length shows two configured global event processors.

Ruby Version

3.2.2

SDK Version

5.9.0

Integration and Its Version

Non-specific

Sentry Config

None needed. Works with sentry-ruby defaults.

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

feat(starfish): update span group breakdown, use metrics (#50086)

This PR updates span group breakdown to use prod data but something funky going on with the data returned by the top n query, bug fix here https://github.com/getsentry/sentry/pull/50105

doesn't implement the updated UI yet

fix(perf-issues): have N+1 detector consider overlapping db spans (#50079)

This change was validated using the Extended N+1 detector (which only records metrics), where we saw an increase of about 8% for N+1s detected.

Remove the check for whether spans overlap, and moev the new _is_slower_than_threshold implementation from the Extended detector to the main detector. Update the N+1 detector tests to confirm that overlapping spans are detected, and remove the duplicated test_n_plus_one_overlapping_db_span_detector.py test file.

feat(starfish): truncate sql query (#50097)

Truncates the query in the db module, the queries were becoming quite long to view

styles(profiling): Align the buttons in span profile details (#50107)

Using baseline means the buttons are misaligned here. Switching to center.

Screenshots

Before

After

feat(span-clusterer): Bump lifetime rules (#50043)

Bump the lifetime of rules that have been applied to span descriptions. Stale rules aren't applied, nor rules that didn't exist before.

feat(starfish): use time spent instead of app impact (#50095)

A couple changes here.

1. Use time spent instead of app impact throughout starfish
2. Add a time spent tooltip explanation
3. Add typing for the table headers.
4. Update some typing to match what they should be based on the query
5. Remove some duplicated types.

feat(functions): Global suspect functions card (#49860)

This introduces a new card to show suspect functions scoped to a project rather than a transaction.

fix(Slack): fix bug resolving in next release (#50126)

This PR fixes a bug where we can't resolve a an issue in the next commit. Resolves https://github.com/getsentry/sentry/issues/50116

fix(functions): Profile functions dataset small fixes (#49919)

Fix type on function duration and ensure is_application is treated as a boolean field.

fix(profiling): draw selected state after grid (#50156)

Fixes https://sentry.slack.com/archives/C02MYEFL2Q7/p1685559790668349

feat(starfish): add p95 to duration charts, use shared title (#50101)

Three main changes are made here

1. Adds p95 to all duration charts in module -> span sample flow
2. Adds a shared colour variable for p95/p50 line graph colours (colours were inconsistent, sometimes p50 was yellow, sometimes orange, etc)
3. Adds a shared titles for duration (Sometimes we just wrote 'Duration', sometimes, we wrote 'Duration (P50)')

fix(sentry-apps): pass org (#50170)

Seems like this was a bug caused from some refactoring of the organization store

fix(proj-creation): Change default team name to 'team-[parsed-email]' (#50123)

Previously, the default team name was default-team-[username]. This had to problem of including the default 32 letter string as the username if the user never changed their sentry username. We instead parse the email username (everything before the @) and use team-[email_username] for shortness and clarity, eg: team-seiji.chew

fix(escalating): Update archive/resolve tooltip copy (#50168)

fixes #50159

fix(query-subscription-consumer): Fix multi processing usage in prod (#50175)

I forgot to pass this boolean through to the subscription consumer. Also adding tags around metrics to differentiate consumers based on group id

feat(dashboard-widget-description-frontend): Added functionality and … (#50162)

Linked Issue: https://github.com/getsentry/sentry/issues/34420

1. Added description textarea in widget builder:

2. Added description to widget previews:

3.Added description to widget viewer modal:

4. Added tests.

Co-authored-by: Abdullah Khan abdullahkhan@PG9Y57YDXQ.local

fix(escalating): Update issue details archive guide copy (#50176)

fix(sort): apply greatest to v2 aggregate_event_score to avoid multiplying by 0 (#50132)

Fixes the scoring so we don't multiply the scores if the aggregate_event_score is 0. Also refactors this function to avoid dupe line.

fix(sort): special aggregation for sorted issue platform issues (#50129)

Workaround to 'support' betterPriority sort for issue platform backed issues.

This basically sets Performance and Profiling issue scores to zero so they end up at the very last in issue search sort order.

Resolves SENTRY-11SS

Revert "fix(query-subscription-consumer): Fix multi processing usage in prod (#50175)"

This reverts commit 3d3e7935946a2b7e7bb5cf397ce3765bcb98a4e4.

Co-authored-by: wedamija 6288560+wedamija@users.noreply.github.com

Another approach

This is something we cannot do today but is worth adding to the backlog, @scefali can you please confirm if I am correct?

Routing to @getsentry/product-owners-settings-integrations for triage, due by Monday, June 5th at 5:00 pm (sfo). ⏲️

Problem Statement

Feedback from Customer:

We have multiple workspaces that each want a separate Sentry App installation but the integration platform supports only 1 auth token per installation for a Sentry organization

Solution Brainstorm

No response

Product Area

Settings - Integrations