Closed hernanmd closed 1 year ago
Hey, sorry for the long wait. I'm not aware that we ever had a version 1.47.0
. I have no idea where that is coming from. If you generated the file with Pharo 9 or 10 and did not load Fuel yourself, then you very likely were using Fuel 4, 4.1.1
specifically.
You should be able to load your file by unloading Fuel 5 first and then loading Fuel 4.1.1
(see readme for details). You will still run into FLBadVersion
, because of the version number mismatch, but you can work around that by adding an exception handler to the loading code and resuming the exception:
[ "load file" ] on: FLBadVersion do: [ :ex | ex resume ]
The version number corresponds to a branch in the Git repository (we used Monticello before moving to Git, so not all versions exist in the Git repository).
This issue has been automatically marked as stale because it has not had recent activity. It will remain open but will probably not come into focus. If you still think this should receive some attention, leave a comment. Thank you for your contributions.
Closing due to inactivity.
I am using Pharo 11 now and when I try to materialize this file I get :
FLBadVersion: Materialization error. Unexpected stream version 1.47.0 where it should be 5.0.6.
So if I am correct I should load the Fuel version matching 1.47.0, materialize the objects, and re-load the current version to serialize them again. However, I did not find a branch that matches this number. I know the version I generated that serialization on was either Pharo 9 or Pharo 10, but I don't know which version to load.
Should 1.47.0 match a branch name in this repository? Any way to get the mappings and/or load expression?