-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
9fe6c6f
commit dd4c5ac
Showing
2 changed files
with
7 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dd4c5ac
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.
Hi @cowtowncoder, this change on
2.9
branch to address #2331 seems to have caused some kind of regression for us in2.9.9.2
- the changelog has it in2.9.9.1
per above, however I believe it's actually been released in2.9.9.2
, although the intention was probably for2.9.10
based on the commit comment.We started getting NPEs on this exact line after this bump
Haven't dug into root cause and reproduced, as I'm not super-familiar with Jackson internals, but we're seeing it on our use with
spring-data-redis
's Jackson2HashMapper in this line hereResolvedRecursiveType
is aJsonNode
with no_referencedType
Any chance of reverting this so we can pick up the CVE fixes, and relook at this for
2.9.10
? Let me know if you'd like me to file an issue and what additional detail would be useful.dd4c5ac
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.
@chadlwilson Ok first of all thank you for reporting this & apologies for breakages. I usually follow fairly conservative approach to fixes late in patch cycle so in hindsight would have made sense to only fix in 2.10.
But one think that'd be great to have would be reproduction, as obviously none of the tests we have catches this?
As to revert, yes, that probably makes sense even tho I think fix/work-around of checking for nulls (I think this is just because resolved type has initial state of not resolved) probably handles it. But there may be more to it.
I probably should do 2.9.9.3, yes, will see how timing looks like.
But one thing first: could you file a new issue for this if you haven't already?
dd4c5ac
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.
Thanks - I haven't raised one but will.
dd4c5ac
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.
Neo4j-OGM HTTP Transport fails with NPE, too. @chadlwilson Did you already create an issue?
dd4c5ac
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.
I created a ticket: #2395 Happens when the Jdk8 module is registered, too.
dd4c5ac
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.
Apologies for the delay - and thanks for raising a ticket @michael-simons.