Skip to content

Conversation

@morganga
Copy link
Contributor

@morganga morganga commented Mar 20, 2022

(fix #3419)

Simply override fillInStackTrace with a noop.

I've added a secondary method _fillInStackTrace to actually fill in the stack trace when throwing a client UnresolvedForwardReferene.

If you prefer I can make this method package private.

@cowtowncoder
Copy link
Member

Excellent, thank you!

Only one practical matter before I merge this: unless I have asked for it, I'd need CLA from here:

https://github.com/FasterXML/jackson/blob/master/contributor-agreement.pdf

(only needs to be done once before the first contribution; it's good for all future PRs)

the usual way is to print, fill & sign, scan/photo, email to info at fasterxml dot com.

Once I have that I'll merge this.

Thank you once again for this contribution!

@cowtowncoder cowtowncoder changed the title Fix #3419 do not generate stack trace for UnresolvedForwardReference … Fix #3419 do not generate stack trace for UnresolvedForwardReference throw internally Mar 21, 2022
@morganga
Copy link
Contributor Author

CLA signed and emailed, thanks.

@cowtowncoder cowtowncoder added this to the 2.14.0 milestone Mar 22, 2022
@cowtowncoder
Copy link
Member

CLA received, will merge, thanks!

@cowtowncoder cowtowncoder merged commit fec520d into FasterXML:2.14 Mar 22, 2022
@cowtowncoder
Copy link
Member

Merged, release notes updated, will be included in 2.14.0.

Thank you very much for this improvement!

@morganga morganga deleted the fix/3419 branch March 22, 2022 09:17
@cowtowncoder cowtowncoder modified the milestones: 2.14.0, 2.13.3 Apr 5, 2022
@cowtowncoder
Copy link
Member

Since this should be safe enough, backported in 2.13.3

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

Successfully merging this pull request may close these issues.

Improve performance of UnresolvedForwardReference for forward reference resolution

2 participants