False positive against Sentry-Trace

[TomBeckett]

Describe the bug

• I have verified that the issue is reproducible against the latest version
  of the project.
• I have searched through existing issues to verify that this issue is not
  already known.

Minimal Reproducible Example

    @SentrySpan
    @Transactional
    @Scheduled(cron = "@hourly")
    @SchedulerLock(name = SYNC_EXERCISES_LOCK_NAME, lockAtLeastFor = "2m", lockAtMostFor = "10m")
    @SentryTransaction(operation = "task")

Produces:

[ERROR]     (see https://error-prone.picnic.tech/bugpatterns/ScheduledTransactionTrace)
[ERROR]   Did you mean '@Trace(dispatcher = true)@SentrySpan'?

Expected behavior

No error should be present. We use Sentry (not New Relic).

Setup

• Mac OS latest.
• Java version 19.0.1
• Error Prone Latest
• Error Prone Support Latest

Additional context

None.

[rickie]

Hey @TomBeckett, thanks for opening this issue!

Good news, we are already working on a fix for that! For context, see #308. There we add an extra check to make sure that an error is thrown only if New Relic is on the classpath. In other words, it should fix your case.

For now, I would suggest to turn off the check as is explained in our documentation.

We will let you know once a fix for this is out.

[TomBeckett]

@rickie Awesome, thank you for the fast response. Is there any ETA on when this may be released?

I ask because I have the more issues/examples just like that thread and don't want to spam issues if they are coming soon 😄

[rickie]

I hope we can do a release ~this week (not making a hard promise though 👀).

Do you mean that you have more related issues or other issues that are not related to this one?
In the latter case, feel free to open more issues 😄.

[rickie]

@TomBeckett we released v0.5.0! So updating should solve the problem 😄. Let us know if you encounter any problem.