Skip to content
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

Jackson 2.9.3 release for Scala module #357

Closed
cowtowncoder opened this issue Dec 9, 2017 · 11 comments
Closed

Jackson 2.9.3 release for Scala module #357

cowtowncoder opened this issue Dec 9, 2017 · 11 comments
Assignees

Comments

@cowtowncoder
Copy link
Member

2.9.3 release:

https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.3

going out, need Scala module too.

@mbknor
Copy link
Member

mbknor commented Dec 10, 2017

[info] UntypedObjectDeserializerTest:
[info] UntypedObjectDeserializer
[info] - should deserialize to an immutable.Map by default
[info] - should honor AbstractTypeResolvers *** FAILED ***
[info]   Map("mData" -> "mValue") was not an instance of scala.collection.immutable.TreeMap, but an instance of scala.collection.immutable.Map$Map1 (UntypedObjectDeserializerTest.scala:52)
[info] Run completed in 498 milliseconds.
[info] Total number of tests run: 2
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 1, failed 1, canceled 0, ignored 0, pending 0
[info] *** 1 TEST FAILED ***
[error] Failed tests:
[error] 	com.fasterxml.jackson.module.scala.deser.UntypedObjectDeserializerTest
[error] (test:testOnly) sbt.TestsFailedException: Tests unsuccessful

This was not as easy as it used to be..
The upgrade to 2.9.3 broke a test, and I have not yet figured out what the problem is and how to fix it...

@cowtowncoder
Copy link
Member Author

cowtowncoder commented Dec 11, 2017

Hmmh. That is unfortunate. And none of databind fixes listed in release notes seem directly related here.
Except perhaps one of:

which could have exposed an existing issue with type compatibility.

@brharrington
Copy link
Contributor

One observation, I hit this problem when running sbt on the command line or running just UntypedObjectDeserializer in the IDE. But if I run all tests in the IDE it passes. Not really sure what difference that would make.

@mbknor
Copy link
Member

mbknor commented Jan 16, 2018

I get the same error both in sbt and in intelliJ.
Please see #359 for more info.

I guess it works in your IDE, since it has not changed from 2.9.2 to 2.9.3.

@brharrington
Copy link
Contributor

I guess it works in your IDE, since it has not changed from 2.9.2 to 2.9.3.

What I'm seeing in the IDE is that:

  • It works if I run all tests.
  • It fails with the same error if I just run UntypedObjectDeserializerTest.

I'm guessing that there is some side effect or test ordering issue that causes it to behave differently in these cases.

@mbknor
Copy link
Member

mbknor commented Jan 16, 2018

@brharrington thanks for that clarification! That means that the problem probably relates to caching and the order of which it is initialized.

@bestcastor
Copy link

https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.4

Jackson release for 2.9.4, included the fix for CVE-2017-17485.

Need Scala module to update to 2.9.4.

@cowtowncoder
Copy link
Member Author

cowtowncoder commented Jan 27, 2018

@bestcastor At this point there is no dedicated maintainer for this module, so any help you (or anyone else with skills, time & interest!) can give in figuring out how to make it happen much appreciated.

Other than that, using 2.9.2of Scala module, with rest of Jackson components at 2.9.4 is the way to go: patch releases are API compatible between each other, and CVE fixes are all in jackson-databind, none in Scala module.

brharrington added a commit to brharrington/jackson-module-scala that referenced this issue Jan 27, 2018
Fixes FasterXML#357. The AbstractTypeResolvers test fails when using
the default.
@brharrington
Copy link
Contributor

The difference I was seeing in the IDE was because the UntypedObjectDeserializer didn't have the @RunWith(classOf[JUnitRunner]) annotation like the other tests so it was skipped when I ran all.

@cowtowncoder
Copy link
Member Author

Ok, I merged the test fix. Does this help at all with problem of failed test(s) of #359?

@mbknor
Copy link
Member

mbknor commented Jan 28, 2018

Version 2.9.4 is now released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants