Ideally we should have a test that catches issues like #37989
Comment From: Wzy19930507
Hi, @philwebb may i join this task?
Comment From: philwebb
I'm sorry @Wzy19930507 but I don't have time to actually look into this one right now. Feel free to have a go at fixing it if you like, but I won't be able to provide much guidance at the moment.
Comment From: Wzy19930507
Hi, @philwebb Because of server need start before client get server metadata(such as ip/port), i need prove that call Container.start before create client bean.
Case to be verified that create client bean after BeanPostProcessor
- LoadTimeWeaverAware
- @Configuration
- ApplicationRunner
But is this feasible?
Comment From: eddumelendez
@philwebb I think this issue can be closed due to has been properly tested in #37989, right?
Comment From: philwebb
I think we ended up manually testing the fix for #37989, I'd like to see if we can an actual integration test that fails the build if we accidentally reintroduce the problem.