Sean P. DeNigris wrote
To a newer user, this could be a confidence-shaking deal breaker.
Workaround:
1. Revert Fuel package to v. 798 i.e. just before version bump
2. Materialize data
3. Reload original Fuel package (currently v. 804)
Glad that worked.
Suggestions:
1. unless/until we have a Fuel migration tool, at minimum, any Fuel version
integrated into latest Pharo must be loadable in the previous Pharo version.
E.g. if Fuel 1.9.4 was loadable in Pharo 3.0, migration would be a bit
awkward, but doable.
That���s a good idea. I���ll make a fix and add a job to the Fuel build to check for that.
Just note that ���loadable��� doesn���t necessarily mean ���usable��� in every sense. Example: the Context class does not exist in Pharo3. Luckily we do have a migration mechanism which allows us to specify which class to use instead of MethodContext during materialization. But: there are some migrations we can���t perform with Fuel (though they���re probably not relevent to most users).
What I want to say is that it���s the users responsibility to make sure that a graph is consistent (whatever the user defines as consistent) after materialization in such a situation. At least for now. Maybe we���ll get to a better place in the future.
2. Maybe more guidance in the default error behavior would help e.g. put up
text suggesting to either a) temporarily downgrade Fuel to whatever version
on first materialization, or b) re-serialize in the image where the data was
serialized after upgrading Fuel
We are aware that this is an open issue [1]. Many people have struggled with this (including myself). Unfortunately, none of the devs (Martin, Mariano and me) have any time to work on time consuming Fuel issues. If you (or anybody else) want to help with this though, I���d be happy to help where I can.
Cheers,
Max
[1]
https://code.google.com/p/fuel/issues/detail?id=207&q=version&colspec=ID%20Type%20Status%20Priority%20Milestone%20Component%20Owner%20Summary