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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: If transaction or span is finished, do not allow to mutate #1940

Merged
merged 2 commits into from
Mar 8, 2022

Conversation

marandaneto
Copy link
Contributor

馃摐 Description

Fix: If transaction or span is finished, do not allow to mutate

馃挕 Motivation and Context

Closes #1840

馃挌 How did you test it?

馃摑 Checklist

  • I reviewed the submitted code
  • I added tests to verify the changes
  • I updated the docs if needed
  • No breaking changes

馃敭 Next steps

@marandaneto marandaneto merged commit 530d17d into main Mar 8, 2022
@marandaneto marandaneto deleted the fix/finish-noop branch March 8, 2022 18:12
@@ -379,6 +415,10 @@ public void setName(@NotNull String name) {
@Deprecated
@ApiStatus.ScheduledForRemoval
public void setRequest(final @Nullable Request request) {
if (root.isFinished()) {
return;
Copy link
Member

Choose a reason for hiding this comment

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

Should we log a warning? It seems like an incorrect instrumentation

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.

if transaction.finish was called, we should not allow calling startChild
3 participants