Skip to content
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.

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

Hsm 43 fix android tests #3417

Closed
wants to merge 1 commit into from
Closed

Hsm 43 fix android tests #3417

wants to merge 1 commit into from

Conversation

lbloder
Copy link
Collaborator

@lbloder lbloder commented May 13, 2024

#skip-changelog

📜 Description

💡 Motivation and Context

💚 How did you test it?

📝 Checklist

  • I reviewed the submitted code.
  • I added tests to verify the changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • Review from the native team if needed.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

@lbloder lbloder changed the base branch from main to 8.x.x May 13, 2024 12:34
Copy link
Member

@adinauer adinauer left a comment

Choose a reason for hiding this comment

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

I think we should go with the new behaviour instead and close this PR in favor of another that fixes the test. See comment below.

@@ -416,8 +416,24 @@ public void close(final boolean isRestarting) {
}

// TODO: should we end session before closing client?
configureScope(ScopeType.CURRENT, scope -> scope.getClient().close(isRestarting));
configureScope(ScopeType.ISOLATION, scope -> scope.getClient().close(isRestarting));
configureScope(
Copy link
Member

Choose a reason for hiding this comment

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

I think it makes more sense to accept the new behaviour of sending out old events on re-init of the SDK.

It's common for Spring Boot applications to also initialize the SDK first via a Sentry logging SDK and then
re-initialize Sentry in the Spring Boot SDK as this setup also reports startup problems to Sentry that happen before the Spring Boot SDK is able to initialize. For this case I think it makes perfect sense to send out data that was created before re-init.

@adinauer
Copy link
Member

Closing this in favor of fixing the test rather than changing behaviour.

@adinauer adinauer closed this May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants