-
Notifications
You must be signed in to change notification settings - Fork 609
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose config to set up the re-transform support explicitly #636
Conversation
…orm support explicitly
For a real workload (Spring Boot application) with ~30 classes to be enhanced. Local env
|
@lujiajing1126 I updated the doc, please take a look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This option might be better changed to enable or disable custom byte-buddy patch, for compatibility reasons. |
Compatible with which part? |
Determine whether to use a custom private static AgentBuilder newAgentBuilder(SWDescriptionStrategy descriptionStrategy) {
final ByteBuddy byteBuddy = new ByteBuddy()
.with(TypeValidation.of(Config.Agent.IS_OPEN_DEBUGGING_CLASS))
.with(new SWAuxiliaryTypeNamingStrategy(NAME_TRAIT))
.with(new SWImplementationContextFactory(NAME_TRAIT));
return new SWAgentBuilderDefault(byteBuddy, new SWNativeMethodStrategy(NAME_TRAIT))
.with(descriptionStrategy);
} |
I don't think we need to expose. This should not be aware ny users. |
I mean the option is |
I know your point. But I doubt they will know what path or our customization mean. |
Like I documented, it should be a straight forward. If there are really some issues of your patch, that is a bug, nothing more |
I agree. I'm just wondering if there's a fallback mechanism that can be enabled if something goes wrong. |
Don't worry. 8.x is safe enough to fall back. 😊 |
Close for now, as we seems to have a solution now. |
CHANGES
log.I am waiting for @lujiajing1126 final report about this case in their environment.