Frank Chen

Thank you @raphw

Seems that I successfully did that by defining a custom attribute for the Advice class and binding that attribute to the dynamic field. Not sure if it's the best way...

@raphw , Thanks for yoru response. I know the `FieldValue` annotation. but since the field name in my case is dynamic, how can I use it in the Advice class?

The comment here I think did the right thing. https://github.com/raphw/byte-buddy/issues/1208#issuecomment-1045792392

Thank you @raphw for your response. In my case, I really need to process the method objects. But I didn't see this `cached` property on `Advice.Origin` annotation. Do I miss...

OK, I will try it. Very appreciate your response.

@raphw It works by defining a customer mapping as below. ```java public class TargetMethodMapping implements Advice.OffsetMapping { @Override public Target resolve(TypeDescription instrumentedType, MethodDescription instrumentedMethod, Assigner assigner, Advice.ArgumentHandler argumentHandler, Sort sort)...

@123liuziming I haven't check whether the fix that Spencer mentioned before works, you can try to use a release that contains that fix. For us, the netty is configured to...

I think this is because your advice class and the field `wechatMiniappFeature` are not declared as `public`.

Should be introduced by #46946 (Linked to the PR for the purpose of knowing when this bug was introduced) https://github.com/ClickHouse/ClickHouse/pull/46946/files#diff-0f4308161ab179a68f01cabfce4dc9e6e4e5f9c1e6c46c37d5adaeaad74e9913L465