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
apparently, there was a change inside NativeClosureManager (jnr-ffi) between version 2.1.9 and 2.1.7. by having web3j v 4.1.0 as a dependency, i accidentally bumped jnr-ffi to 2.1.9 which caused jnr-fuse to break (but only for readdir). Fixed this via a custom resolutionStrategy in my build.gradle. It would be nice to have compatibility with jnr-ffi 2.1.9
The cause is the call
Field classLoaderField = NativeClosureManager.class.getDeclaredField("classLoader");
which happens in ClosureHelper, NativeClosureManager appears to have changed in its internal structure.
This is an issue because it is easy to accidentally bump jnr-ffi to 2.1.9 f.ex. when depending on other libs that declare it.
The text was updated successfully, but these errors were encountered:
apparently, there was a change inside NativeClosureManager (jnr-ffi) between version 2.1.9 and 2.1.7. by having web3j v 4.1.0 as a dependency, i accidentally bumped jnr-ffi to 2.1.9 which caused jnr-fuse to break (but only for readdir). Fixed this via a custom resolutionStrategy in my build.gradle. It would be nice to have compatibility with jnr-ffi 2.1.9
The cause is the call
which happens in ClosureHelper, NativeClosureManager appears to have changed in its internal structure.
This is an issue because it is easy to accidentally bump jnr-ffi to 2.1.9 f.ex. when depending on other libs that declare it.
The text was updated successfully, but these errors were encountered: