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
Tests with @Rule still use JUnit 4 vintage #2605
Conversation
Report metrics when unusually large strings are parsed
[skip ci]
InstrumentedJsonFactory sets the expected 'JSON' format name
[skip ci]
Json parser string length metrics are tagged by format
[skip ci]
Increase string-length observability thresholds
[skip ci]
Upgrade Undertow to 2.2.24.Final
Interning introduces excessive contention
[skip ci]
Add public JsonFactory factories to ObjectMappers
[skip ci]
Use a TypeFactory backed by a Caffeine Cache
[skip ci]
Add TypeFactory cache instrumentation
[skip ci]
#2595) Opt out of the TypeFactory cache until we can resolve cache contention
[skip ci]
…ing TypeFactories (#2597) ObjectMappers.withDefaultModules(ObjectMapper) does not replace existing TypeFactories with state from registered modules
[skip ci]
…2601) Apply a large StreamReadConstraints maxStringLength to reduce friction in preparation for jackson 2.15 adoption
[skip ci]
Opt out of canonicalization in Conjure JsonFactories
[skip ci]
improvement: | ||
description: Json parser string length metrics are tagged by format | ||
links: | ||
- https://github.com/palantir/conjure-java-runtime/pull/2571 |
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.
Looks like something went sideways in a rebase/merge
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.
Ugh, the merge of origin/develop seems to have gone sideways, I may just put together a separate PR
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.
Moving to #2616
Moving to #2616 |
Before this PR
JUnit 5 excavator #2485 is stuck.
2093 tests complete on
develop
check taskAfter this PR
Merged origin/develop into this branch and updated tests still using
@Rule
to still use JUnit 4 vintage. This is a smaller change than #2495 that completely eradicates JUnit 4, so targeting this sooner to unblock excavator.2093 tests complete on this branch's
check
task==COMMIT_MSG==
Tests with @rule still use JUnit 4 vintage
==COMMIT_MSG==
Possible downsides?