yuwen
yuwen
@earthquakesan I have the same problem, Below is my namenode log 125 2018-10-12 17:00:19,363 INFO org.apache.hadoop.hdfs.server.blockmanagement.CacheReplicationMonitor: Rescanning after 30008 milliseconds 126 2018-10-12 17:00:19,363 INFO org.apache.hadoop.hdfs.server.blockmanagement.CacheReplicationMonitor: Scanned 0 directive(s) and 0...
After I removed the `-target:version` option, the packaging ended normally. But um why is that?
The top of the exception stack trace shows that the error comes from `MethodRegistry#prepare`. This commit [c66e3086eb075e](https://github.com/raphw/byte-buddy/commit/c66e3086eb075e479f78c0179c48b5717bc75a85) attempted to fix this issue. Have you tried validating it with the latest...
because you are trying to delegatete a method `getA` which does not exist in A.class. Try: 1. define a method `getA()` in A.class. 2. or remove the @SuperCall in AInterceptor....
[Byte Buddy does not require target methods to be named equally to a source method](https://bytebuddy.net/#/tutorial:~:text=Byte%20Buddy%20does%20not%20require%20target%20methods%20to%20be%20named%20equally%20to%20a%20source%20method). the method `String getA()` can be delegated to `AInterceptor.toString()`. You can get an `Unloaded` after...
After calling `installOn`, you will get a `ResettableClassFileTransformer`, you can remove the ClassFileTransformer and retransform the classes by calling the `reset` method. You can use `AgentBuilder#with(TransformerDecorator)` to specify a decorator...
Perhaps it's because the internal implementation of `ElementMatchers.nameMatches(java.lang.String)` further relies on `java.util.regex.Pattern`. If you already have the specific class name, have you tried using `ElementMatchers.named(java.lang.String)` for matching instead?
ByteBuddy does not directly provide an API for this operation. You need to leverage the visitors provided by ASM to achieve this. You can refer to the suggested approach here...
I have encountered this issue before. If I remember correctly, proguard regenerates stack frame information for branch code and exception blocks during the `preverify` stage. The format of the regenerated...
This looks like a BUG, you may need to bypass `TypeValidation` now `new ByteBuddy().with(TypeValidation.DISABLED)`