Handle invalid CBOR content like `[ 0x84 ]` (incomplete array) #240

Closed

Closed

Handle invalid CBOR content like [ 0x84 ] (incomplete array)#240

Labels

Milestone

Member

(inspired by FasterXML/jackson-databind#3032)

Looks like there are types of invalid documents that do not trigger decoding exception for parser, but should.

added

on Jan 30, 2021

mentioned this

on Jan 30, 2021

Prevent NullPointerException on null tokens FasterXML/jackson-databind#3032

modified the milestones: 2, 2.12.2

on Jan 30, 2021

added a commit that references this issue

on Jan 30, 2021

changed the title ~~[-]Handle invalid CBOR content like `[ 0x84 ]` (single byte doc)[/-]~~ Handle invalid CBOR content like `[ 0x84 ]` (incomplete array)

on Jan 30, 2021

added a commit that references this issue

on Jan 30, 2021

and update release notes too wrt #240

closed this as completedin 0659e8c

on Jan 30, 2021

added 2 commits that reference this issue

on Jan 30, 2021

Bit more work for #236 and #240

Complete error reporting improvements (mostly for #240)

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

Type

No type

Projects

No projects

Milestone

2.12.2No due date

Relationships

None yet

Development

No branches or pull requests

Participants