-
Notifications
You must be signed in to change notification settings - Fork 144
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
InvalidTypeIdException thrown after kork version bump #1015
Comments
@jonsie Do you know what was introduced in kork 7.35.0 that could affect deserialization behavior in keel? |
I suspected a change in the version of the jackson libraries. I looked at that kork PR and didn't see anything obvious that might cause our version to change, but when looking at our gradle scripts we're not pinning the version of those libs anywhere, which means they could simply have changed because a new version was published and no one would notice. But... we're on FWIW, the versions of jackson from all the dependencies we pull are all over the place, so I still think it might be worth digging a little more. Also, the fact that we're not pinning the version, while ensuring that we stay up-to-date, is bound to cause us problems even if the library authors are very good at sticking with semantic versioning. Example:
|
This should get fixed by #1017. |
Not fixed by #1017. Still debugging. |
It looks like the |
The issue has been diagnosed as an interaction between Keel and the Kork plugin manager. @luispollo is working on a fix. |
Starting with kork version 7.35.0, keel regularly throws the following exception if run against the prestaging database:
Complete stack trace
Diagnosis: interaction with SpinnakerPluginManager
The SpinnakerPluginManager is instantiating the KeelApplication bean too early in the life cycle, leading to the
@PostConstuct
annotated methods of KeelApplication to not be invoked.Recommended fix by @robzienert is to move all extraneous logic away from the KeelApplication class and onto a different class that is not the main entrypoint.
The text was updated successfully, but these errors were encountered: