If there are 2 methods in the same class with the same name but different jvm signatures, they will share the same map/counter in the context of selective logging.
Example :
Process counter is set to "2".
Class A has methods m1() and m1(int) [same names but different signatures]
DirectInvoking m1() will yield a candidate, calling m1(int) right after that will not.
Reproduction steps
Run unlogged-spring-maven-demo with a counter of your choice
DirectInvoke generateReferralCode from org.unlogged.demo.utils.ReferralUtils -> generates candidate
DirectInvoke generateReferralCode(int customLimit) next, there will be no candidate
Expected behavior
For methods with different signatures to have different counters/maps.
Describe the bug
If there are 2 methods in the same class with the same name but different jvm signatures, they will share the same map/counter in the context of selective logging.
Example : Process counter is set to "2". Class A has methods m1() and m1(int) [same names but different signatures]
DirectInvoking m1() will yield a candidate, calling m1(int) right after that will not.
Reproduction steps
unlogged-spring-maven-demo
with a counter of your choicegenerateReferralCode
fromorg.unlogged.demo.utils.ReferralUtils
-> generates candidategenerateReferralCode(int customLimit)
next, there will be no candidateExpected behavior
For methods with different signatures to have different counters/maps.
Additional context
No response