-
Notifications
You must be signed in to change notification settings - Fork 574
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
Problems with Strand.park (minimal example) (jdk1.8.0_121, quasar-0.7.7) #255
Comments
Okay, this just came up with |
0.7.7 introduced some problems in |
do you have an ETA for 0.7.8 ?
…------ Original Message ------
From: "pron" <notifications@github.com>
To: "puniverse/quasar" <quasar@noreply.github.com>
Cc: "Subscribed" <subscribed@noreply.github.com>
Sent: 21/03/2017 14:31:16
Subject: Re: [puniverse/quasar] Problems with Strand.park (minimal
example) (jdk1.8.0_121, quasar-0.7.7) (#255)
0.7.7 introduced some problems in verifyInstrumentation that were
hopefully addressed in 0.7.8. Can you try 0.7.8-SNAPSHOT?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#255 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEBVpKaXMlDKiXbRtqC_nwMDtQD_wddaks5rn980gaJpZM4MhdE9>.
|
I tried |
The problem seems to be here, the call site is A fix should probably check that the relevant method ( |
We have also many false positive warnings in 0.7.7, so we downgraded to 0.7.6. I try current 0.7.8 today and it's same, still totally useless for us, we can't find real problems in tons of false alarms. |
The following minimal snippet produces the uninstrumented warning at
Strand.park
:The text was updated successfully, but these errors were encountered: