You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that ObjectInputStream is caller sensitive but is not marked as such. If you manually create an ObjectInputStream and then use it to read objects from a jar loaded in the class path it will fail with class not found even through the class is clearly available. If the same calls are made from a class called from JPype which just adds an intermediate layer, the same calls work.
This will require a special catch for this one constructor. Not sure how much effort to put on this one.
The text was updated successfully, but these errors were encountered:
Thrameos
added
the
bug
Unable to deliver desired behavior (crash, fail, untested)
label
Jul 20, 2020
It appears that ObjectInputStream is caller sensitive but is not marked as such. If you manually create an ObjectInputStream and then use it to read objects from a jar loaded in the class path it will fail with class not found even through the class is clearly available. If the same calls are made from a class called from JPype which just adds an intermediate layer, the same calls work.
This will require a special catch for this one constructor. Not sure how much effort to put on this one.
The text was updated successfully, but these errors were encountered: