You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code introduced in the commit b589ced seems to have a bug in functionParams method.
The comment from the commit:
The functionParams method has to filter out JVM bridge methods to ensure
the correct version of the apply() method (with type parameter
information) is captured. Function objects only have one defined method
named apply() so taking the head of the list should always be safe.
It turns out that there may be more methods defined, e.g. inner, helper methods or synthetic methods when accessing Step's variables. In that case taking head after filtering out bridge methods is not enough. Cucumber tests fail randomly because getDeclaredMethods returns Methods without sorting or any particular order.
A quick solution is to add getName to filter but maybe there is a better fix for that.
The code introduced in the commit b589ced seems to have a bug in functionParams method.
The comment from the commit:
It turns out that there may be more methods defined, e.g. inner, helper methods or synthetic methods when accessing Step's variables. In that case taking head after filtering out bridge methods is not enough. Cucumber tests fail randomly because getDeclaredMethods returns Methods without sorting or any particular order.
A quick solution is to add getName to filter but maybe there is a better fix for that.
The text was updated successfully, but these errors were encountered: