Crash in jackson deserialization of suggestion updates #9876
Comments
|
Fixed by #9885 |
|
I don't think this has been fixed. I can still experience it. |
Using a fully qualified name for type identifier does not play well when dealing with different classloaders (classes are not recognized as equal/subtypes). Closes #9876. Likely also affecting #9306. # Important Notes There appears to be a number of cases loosely related issues on that subject. Gave up on adding a test cases to simulate the problem but I could no longer reproduce it with LS/runtime on a live project. ``` [org.enso.languageserver.runtime.RuntimeConnector$Endpoint] Failed to deserialize runtime API envelope com.fasterxml.jackson.databind.exc.InvalidTypeIdException: Could not resolve type id 'org.enso.polyglot.data.Tree$Node' as a subtype of `org.enso.polyglot.data.Tree$Node<org.enso.polyglot.runtime.Runtime$Api$SuggestionUpdate>`: Not a subtype at [Source: (byte[])[6718 bytes]; byte offset: #394] (through reference chain: org.enso.polyglot.runtime.Runtime$Api$Response["payload"]->org.enso.polyglot.runtime.Runtime$Api$SuggestionsDatabaseModuleUpdateNotification["updates"]->org.enso.polyglot.data.Tree$Root["children"]->com.fasterxml.jackson.module.scala.deser.GenericFactoryDeserializerResolver$BuilderWrapper[0]) at org.enso.IsolatedClassLoader//com.fasterxml.jackson.databind.exc.InvalidTypeIdException.from(InvalidTypeIdException.java:43) ``` appears to be gone.
|
Hubert Plociniczak reports a new STANDUP for the provided date (2024-05-14): Progress: Debugging crash in jackson deserialization. Unable to reproduce with a unit case which hinders investigation. In the end turned out to be an issue with class-/module- loaders. It should be finished by 2024-05-15. Next Day: Next day I will be working on the #9876 task. Prepare PR, back to cloud issues |
|
Hubert Plociniczak reports a new STANDUP for the provided date (2024-05-15): Progress: Prepared PR. Back to debugging cloud performance issues. Profiling data appears to be wrong, trying to add more info to investigate the problem. It should be finished by 2024-05-15. Next Day: Next day I will be working on the #9789 task. Continue the investigation. |
Using a fully qualified name for type identifier does not play well when dealing with different classloaders (classes are not recognized as equal/subtypes). Closes #9876. Likely also affecting #9306. # Important Notes There appears to be a number of cases loosely related issues on that subject. Gave up on adding a test cases to simulate the problem but I could no longer reproduce it with LS/runtime on a live project. ``` [org.enso.languageserver.runtime.RuntimeConnector$Endpoint] Failed to deserialize runtime API envelope com.fasterxml.jackson.databind.exc.InvalidTypeIdException: Could not resolve type id 'org.enso.polyglot.data.Tree$Node' as a subtype of `org.enso.polyglot.data.Tree$Node<org.enso.polyglot.runtime.Runtime$Api$SuggestionUpdate>`: Not a subtype at [Source: (byte[])[6718 bytes]; byte offset: #394] (through reference chain: org.enso.polyglot.runtime.Runtime$Api$Response["payload"]->org.enso.polyglot.runtime.Runtime$Api$SuggestionsDatabaseModuleUpdateNotification["updates"]->org.enso.polyglot.data.Tree$Root["children"]->com.fasterxml.jackson.module.scala.deser.GenericFactoryDeserializerResolver$BuilderWrapper[0]) at org.enso.IsolatedClassLoader//com.fasterxml.jackson.databind.exc.InvalidTypeIdException.from(InvalidTypeIdException.java:43) ``` appears to be gone.
Encountered while debugging #9789
Maybe related to a recent change of #9852
The text was updated successfully, but these errors were encountered: