Skip to content

Commit 3b965a8

Browse files
authored
Merge branch 'main' into feat/speed-up-tests
2 parents 618dfa2 + 7314dbe commit 3b965a8

File tree

6 files changed

+258
-38
lines changed

6 files changed

+258
-38
lines changed

.cursor/rules/deduplication.mdc

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
alwaysApply: false
3+
description: Java SDK Event deduplication
4+
---
5+
6+
# Java SDK Event deduplication
7+
8+
To avoid sending the same error multiple times, there is deduplication logic in place in the SDK.
9+
Duplicate captures can happen due to multiple integrations capturing the exception as well as additional manual calls to `Sentry.captureException`.
10+
11+
Deduplication is performed in `DuplicateEventDetectionEventProcessor` which returns `null` when it detects a duplicate event causing it to be dropped.
12+
13+
The `enableDeduplication` option can be used to opt out of deduplication. It is enabled by default.

.cursor/rules/e2e_tests.mdc

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
alwaysApply: false
3+
description: Java SDK End to End Tests
4+
---
5+
6+
# Java SDK End to End Tests (System Tests)
7+
8+
The samples in the `sentry-samples` directory are used to run end to end tests against them.
9+
10+
There is a python script (`system-test-runner.py`) that can be used to run one (using `--module SAMPLE_NAME`) or all (using `--all`) system tests.
11+
12+
The script has an interactive mode (`-i`) which allows selection of test setups to execute, whether to run the tests or just prepare infrastructure for testing from IDE.
13+
14+
The tests run a mock Sentry server via `system-test-sentry-server.py`. Any system under test will then have a DSN set that reflects this local mock server like `http://502f25099c204a2fbf4cb16edc5975d1@localhost:8000/0`.
15+
By using this local DSN, the system under test sends events to the local mock server.
16+
The tests can then use `TestHelper` to assert envelopes that were received by the mock server.
17+
`TestHelper` uses HTTP requests to retrieve the JSON payload of the received events and deserialize them back to objects for easier assertion.
18+
Tests can then assert events, transactions, logs etc. similar to how they would appear in `beforeSend` and similar callbacks.
19+
20+
`TestHelper` has a lot of helper methods for asserting, e.g. by span name, log body etc.
21+
22+
The end to end tests either expect the system under test to either be running on a server or call `java -jar` to execute a CLI system under test.
23+
24+
For Spring Boot, we spin up the Spring Boot server. The tests then send requests to that server and assert what is sent to Sentry.
25+
26+
End to end tests are also executed on CI using a matrix build, as defined in `.github/workflows/system-tests-backend.yml`.
27+
28+
Some of the samples are tested in multiple ways, e.g. with OpenTelemetry Agent auto init turned on and off.

.cursor/rules/overview_dev.mdc

Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
alwaysApply: true
3+
description: Sentry Java SDK - Development Rules Overview
4+
---
5+
6+
# Sentry Java SDK Development Rules
7+
8+
## Always Applied Rules
9+
10+
These rules are automatically included in every conversation:
11+
- **coding.mdc**: General contributing guidelines, build commands, and workflow rules
12+
13+
## Domain-Specific Rules (Fetch Only When Needed)
14+
15+
Use the `fetch_rules` tool to include these rules when working on specific areas:
16+
17+
### Core SDK Functionality
18+
- **`scopes`**: Use when working with:
19+
- Hub/Scope management, forking, or lifecycle
20+
- `Sentry.getCurrentScopes()`, `pushScope()`, `withScope()`
21+
- `ScopeType` (GLOBAL, ISOLATION, CURRENT)
22+
- Thread-local storage, scope bleeding issues
23+
- Migration from Hub API (v7 → v8)
24+
25+
- **`deduplication`**: Use when working with:
26+
- Duplicate event detection/prevention
27+
- `DuplicateEventDetectionEventProcessor`
28+
- `enableDeduplication` option
29+
30+
- **`offline`**: Use when working with:
31+
- Caching, envelope storage/retrieval
32+
- Network failure handling, retry logic
33+
- `AsyncHttpTransport`, `EnvelopeCache`
34+
- Rate limiting, cache rotation
35+
- Android vs JVM caching differences
36+
37+
### Integration & Infrastructure
38+
- **`opentelemetry`**: Use when working with:
39+
- OpenTelemetry modules (`sentry-opentelemetry-*`)
40+
- Agent vs agentless configurations
41+
- Span processing, sampling, context propagation
42+
- `OtelSpanFactory`, `SentrySpanExporter`
43+
- Tracing, distributed tracing
44+
45+
### Testing
46+
- **`e2e_tests`**: Use when working with:
47+
- System tests, sample applications
48+
- `system-test-runner.py`, mock Sentry server
49+
- End-to-end test infrastructure
50+
- CI system test workflows
51+
52+
## Usage Guidelines
53+
54+
1. **Start minimal**: Only include `coding.mdc` (auto-applied) for general tasks
55+
2. **Fetch on-demand**: Use `fetch_rules ["rule_name"]` when you identify specific domain work
56+
3. **Multiple rules**: Fetch multiple rules if task spans domains (e.g., `["scopes", "opentelemetry"]` for tracing scope issues)
57+
4. **Context clues**: Look for these keywords in requests to determine relevant rules:
58+
- Scope/Hub/forking → `scopes`
59+
- Duplicate/dedup → `deduplication`
60+
- OpenTelemetry/tracing/spans → `opentelemetry`
61+
- Cache/offline/network → `offline`
62+
- System test/e2e/sample → `e2e_tests`

.cursor/rules/scopes.mdc

Lines changed: 112 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,112 @@
1+
---
2+
alwaysApply: false
3+
description: Java SDK Hubs and Scopes
4+
---
5+
# Java SDK Hubs and Scopes
6+
7+
## `Scopes`
8+
9+
`Scopes` implements `IScopes` and manages three `Scope` instances, `global`, `isolation` and `current` scope.
10+
For some data, all three `Scope` instances are combined, for others, a certain one is used exclusively and for some we look at each scope in a certain order and use the data of the first scope that has the data set. This logic is contained in `CombinedScopeView`.
11+
Data itself is stored on `Scope` instances.
12+
`Scopes` also has a `parent` field, linking the `Scopes` it was forked off of and a `creator` String, explaining why it was forked.
13+
14+
## `Hub`
15+
16+
Up until major version 7 of the Java SDK the `IHub` interface was a central part of the SDK.
17+
In major version 8 we replaced the `IHub` interface with `IScopes`. `IHub` has been deprecated.
18+
While there is some bridging code in place to allow for easier migration, we are planning to remove it in an upcoming major.
19+
20+
## Scope Types
21+
22+
We have introduced some new Scope types in the SDK, allowing for better control over what data is attached where.
23+
Previously there was a stack of scopes that was pushed and popped.
24+
Instead we now fork scopes for a given lifecycle and then restore the previous scopes.
25+
Since Hub is gone, it is also never cloned anymore.
26+
Separation of data now happens through the different scope types while making it easier to manipulate exactly what you need without having to attach data at the right time to have it apply where wanted.
27+
28+
### Global Scope
29+
30+
Global scope is attached to all events created by the SDK.
31+
It can also be modified before Sentry.init has been called.
32+
It can be manipulated using `Sentry.configureScope(ScopeType.GLOBAL, (scope) -> { ... })`.
33+
34+
Global scope can be retrieved from `Scopes` via `getGlobalScope`. It can also be retrieved directly via `Sentry.getGlobalScope`.
35+
36+
### Isolation Scope
37+
38+
Isolation scope can be used e.g. to attach data to all events that come up while handling an incoming request.
39+
It can also be used for other isolation purposes.
40+
It can be manipulated using `Sentry.configureScope(ScopeType.ISOLATION, (scope) -> { ... })`.
41+
The SDK automatically forks isolation scope in certain cases like incoming requests, CRON jobs, Spring `@Async` and more.
42+
43+
Isolation scope can be retrieved from `Scopes` via `getIsolationScope`.
44+
45+
### Current scope
46+
47+
Current scope is forked often and data added to it is only added to events that are created while this scope is active.
48+
Data is also passed on to newly forked child scopes but not to parents.
49+
50+
Current scope can be retrieved from `Scopes` via `getScope`.
51+
52+
## Storage of `Scopes`
53+
54+
`Scopes` are stored in a `ThreadLocal` by default (NOTE: this is different for OpenTelemetry, see opentelemetry.mdc).
55+
This happens through `Sentry.scopesStorage` and `DefaultScopesStorage`.
56+
57+
The lifetime of `Scopes` in the thread local is managed by `ISentryLifecycleToken`.
58+
When the scopes are forked, they are stored into the `ThreadLocal` and a `ISentryLifecycleToken` is returned.
59+
When the `Scopes` are no longer needed, e.g. because a request is finished, `ISentryLifecycleToken.close` can be called to restore the previous state of the `ThreadLocal`.
60+
61+
## Old versions of the Java SDK
62+
63+
There were several implementations of the `IHub` interface:
64+
- `Hub` managed a stack of `Scope` instances, which were pushed and popped.
65+
- A `Hub` could be cloned, meaning there could be multiple stacks of scopes active, e.g. for two separate requests being handled in a server application.
66+
67+
### Migrating to major version 8 of the SDK
68+
69+
`IHub` has been replaced by `IScopes`
70+
`HubAdapter` has been replaced by `ScopesAdapter`
71+
`Hub.clone` should be replaced by using `pushScope` or `pushIsolationScope`
72+
`Sentry.getCurrentHub` has been replaced by `Sentry.getCurrentScopes`
73+
`Sentry.popScope` has been deprecated. Instead `close` should be called on the `ISentryLifecycleToken` returned e.g. by `pushScope`. This can also be done in a `try-with-resource` block.
74+
75+
## `globalHubMode`
76+
The SDK has a `globalHubMode` option which affects forking behaviour of the SDK.
77+
78+
Android has `globalHubMode` enabled by default.
79+
For JVM Desktop applications, `globalHubMode` can be used.
80+
For JVM Backend applications (servers) we discourage enabling `globalHubMode` since it will cause scopes to bleed into each other. This can e.g. mean that state from request A leaks into request B and events sent to Sentry contain a mix of both request A and B potentially rendering the data useless.
81+
82+
### Enabled
83+
84+
If `globalHubMode` is enabled, the SDK avoids forking scopes.
85+
86+
This means, retrieving current scopes on a thread where specific scopes do not exist yet for the thread, the root scopes are not forked but returned directly.
87+
The SDK also doesn't fork scopes when `Sentry.pushScope`, `Sentry.pushIsolation`, `Sentry.withScope` or `Sentry.withIsolationScope` are executed.
88+
89+
The suppression of forking via `globalHubMode` only applies when using `Sentry` static API or `ScopesAdapter`.
90+
In case the `Scopes` instance is accessed directly, forking will happen as if `globalHubMode` is disabled.
91+
However, while it's possible to use `Sentry.setCurrentScopes` it does not have any effect due to `Sentry.getCurrentScopes` directly returning `rootScopes` if `globalHubMode` is enabled.
92+
This means the forked scopes have to be managed manually, e.g. by keeping a reference and accessing Sentry API via the reference instead of using static API.
93+
94+
`ScopesAdapter` makes use of the static `Sentry` API internally. It allows us to access the correct scopes for the current context without passing it along explicitly. It also makes testing easier.
95+
96+
### Disabled
97+
98+
If `globalHubMode` is disabled, the SDK forks scopes freely, e.g. when:
99+
- `Sentry.getCurrentScopes()` is executed on a Thread where no specific scopes for that thread have been stored yet. In this case the SDK will fork `rootScopes` (stored in a `Sentry` static property).
100+
- `withScope` or `withIsolationScope` are executed
101+
- `pushScope` or `pushIsolationScope` are executed
102+
103+
## `defaultScopeType`
104+
105+
The `defaultScopeType` controls which `Scope` instance is being used for writing to and reading from as a default value.
106+
When using API like `Sentry.setTag` the SDK adds that tag to the default `Scope`.
107+
108+
This also ensures, customers who migrate to the latest SDK version and already have `Sentry.configureScope` invocations in place, will now write to the default `Scope` instance that was chosen.
109+
110+
The default value for `defaultScopeType` is `ISOLATION` scope for JVM and `CURRENT` scope for Android.
111+
112+
Which fields are written/read from/to `defaultScopeType` is controlled in `CombinedScopeView`.

CHANGELOG.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@
66

77
- Add support for Spring Boot 4 and Spring 7 ([#4601](https://github.com/getsentry/sentry-java/pull/4601))
88
- NOTE: Our `sentry-opentelemetry-agentless-spring` is not working yet for Spring Boot 4. Please use `sentry-opentelemetry-agent` until OpenTelemetry has support for Spring Boot 4.
9+
- Replace `UUIDGenerator` implementation with Apache licensed code ([#4662](https://github.com/getsentry/sentry-java/pull/4662))
910

1011
## 8.20.0
1112

@@ -30,13 +31,19 @@
3031

3132
## 8.19.1
3233

34+
> [!Warning]
35+
> Android: This release is incompatible with API levels below 26. We recommend using SDK version 8.20.0 or higher instead.
36+
3337
### Fixes
3438

3539
- Do not store No-Op scopes onto OpenTelemetry Context when wrapping ([#4631](https://github.com/getsentry/sentry-java/pull/4631))
3640
- In 8.18.0 and 8.19.0 the SDK could break when initialized too late.
3741

3842
## 8.19.0
3943

44+
> [!Warning]
45+
> Android: This release is incompatible with API levels below 26. We recommend using SDK version 8.20.0 or higher instead.
46+
4047
### Features
4148

4249
- Add a `isEnableSystemEventBreadcrumbsExtras` option to disable reporting system events extras for breadcrumbs ([#4625](https://github.com/getsentry/sentry-java/pull/4625))
Lines changed: 36 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,19 @@
11
/*
2-
* Copyright (c) 2003, 2022, Oracle and/or its affiliates. All rights reserved.
3-
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
2+
* Adapted from: http://github.com/baomidou/dynamic-datasource/blob/bae2677b83abad549e3ddf41b286749515360e7b/dynamic-datasource-spring/src/main/java/com/baomidou/dynamic/datasource/tx/LocalTxUtil.java
43
*
5-
* This code is free software; you can redistribute it and/or modify it
6-
* under the terms of the GNU General Public License version 2 only, as
7-
* published by the Free Software Foundation. Oracle designates this
8-
* particular file as subject to the "Classpath" exception as provided
9-
* by Oracle in the LICENSE file that accompanied this code.
4+
* Copyright © 2018 organization baomidou
105
*
11-
* This code is distributed in the hope that it will be useful, but WITHOUT
12-
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
13-
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
14-
* version 2 for more details (a copy is included in the LICENSE file that
15-
* accompanied this code).
6+
* Licensed under the Apache License, Version 2.0 (the "License");
7+
* you may not use this file except in compliance with the License.
8+
* You may obtain a copy of the License at
169
*
17-
* You should have received a copy of the GNU General Public License version
18-
* 2 along with this work; if not, write to the Free Software Foundation,
19-
* Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
10+
* http://www.apache.org/licenses/LICENSE-2.0
2011
*
21-
* Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
22-
* or visit www.oracle.com if you need additional information or have any
23-
* questions.
12+
* Unless required by applicable law or agreed to in writing, software
13+
* distributed under the License is distributed on an "AS IS" BASIS,
14+
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
15+
* See the License for the specific language governing permissions and
16+
* limitations under the License.
2417
*/
2518

2619
package io.sentry.util;
@@ -35,36 +28,41 @@ public final class UUIDGenerator {
3528

3629
@SuppressWarnings("NarrowingCompoundAssignment")
3730
public static long randomHalfLengthUUID() {
38-
Random random = SentryRandom.current();
31+
Random ng = SentryRandom.current();
3932
byte[] randomBytes = new byte[8];
40-
random.nextBytes(randomBytes);
41-
randomBytes[6] &= 0x0f; /* clear version */
42-
randomBytes[6] |= 0x40; /* set to version 4 */
43-
33+
ng.nextBytes(randomBytes);
34+
// clear version
35+
randomBytes[6] &= 0x0f;
36+
// set to version 4
37+
randomBytes[6] |= 0x40;
4438
long msb = 0;
45-
46-
for (int i = 0; i < 8; i++) msb = (msb << 8) | (randomBytes[i] & 0xff);
47-
39+
for (int i = 0; i < 8; i++) {
40+
msb = (msb << 8) | (randomBytes[i] & 0xff);
41+
}
4842
return msb;
4943
}
5044

5145
@SuppressWarnings("NarrowingCompoundAssignment")
5246
public static UUID randomUUID() {
53-
Random random = SentryRandom.current();
47+
Random ng = SentryRandom.current();
5448
byte[] randomBytes = new byte[16];
55-
random.nextBytes(randomBytes);
56-
randomBytes[6] &= 0x0f; /* clear version */
57-
randomBytes[6] |= 0x40; /* set to version 4 */
58-
randomBytes[8] &= 0x3f; /* clear variant */
59-
randomBytes[8] |= (byte) 0x80; /* set to IETF variant */
60-
49+
ng.nextBytes(randomBytes);
50+
// clear version
51+
randomBytes[6] &= 0x0f;
52+
// set to version 4
53+
randomBytes[6] |= 0x40;
54+
// clear variant
55+
randomBytes[8] &= 0x3f;
56+
// set to IETF variant
57+
randomBytes[8] |= 0x80;
6158
long msb = 0;
6259
long lsb = 0;
63-
64-
for (int i = 0; i < 8; i++) msb = (msb << 8) | (randomBytes[i] & 0xff);
65-
66-
for (int i = 8; i < 16; i++) lsb = (lsb << 8) | (randomBytes[i] & 0xff);
67-
60+
for (int i = 0; i < 8; i++) {
61+
msb = (msb << 8) | (randomBytes[i] & 0xff);
62+
}
63+
for (int i = 8; i < 16; i++) {
64+
lsb = (lsb << 8) | (randomBytes[i] & 0xff);
65+
}
6866
return new UUID(msb, lsb);
6967
}
7068
}

0 commit comments

Comments
 (0)