Closed vietj closed 3 years ago
@vietj this is not a regression from my patch (actually the PR is not merged yet)
The problem comes from:
It doesn't work because the toJson
method in DropwizardMetricsOptions
does not take several fields into account:
I'm not sure why actually because when parsing JSON these fields are taken into account.
ok I'll ahve a look myself then
On Tue, Feb 16, 2021 at 10:24 PM Thomas Segismont notifications@github.com wrote:
@vietj https://github.com/vietj this is not a regression from my patch (actually the PR https://github.com/eclipse-vertx/vert.x/pull/3810 is not merged yet)
The problem comes from:
It doesn't work because the toJson method in DropwizardMetricsOptions does not take several fields into account:
I'm not sure why actually because when parsing JSON these fields are taken into account.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vert-x3/issues/issues/575#issuecomment-780126731, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABXDCXNCBJA7XR4472XQK3S7LPATANCNFSM4XWYMV7Q .
thanks @tsegismont you are totally right: https://github.com/vert-x3/vertx-dropwizard-metrics/issues/104
Currently vertx-dropwizard-metrics build fails because custom options cannot be loaded from the options as they are replaced sometimes with a new instance.
This build shows the issue : https://github.com/vert-x3/vertx-dropwizard-metrics/runs/1908022188?check_suite_focus=true , e.g
It can be reproduced by simply running this test locally too.
I think we are missing a corresponding test in vertx-core.