-
Notifications
You must be signed in to change notification settings - Fork 39
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
BSON file saves on 64bit system can not be loaded on 32bit system #41
Comments
Addendum: if it wasn't clear it is the Dict's type param that is deserializing wrong |
The MWE of And it works either direction. In the attached .zip are files from both 32bit and 64 bit systems that have that MWE. You just need to call Note that: But that
The fact that the two files All I can think is that somewhere a I am going to stop trying to debug it for now. |
AHAHAHA When the Int literals have different types. Short-term hack is to make Integer Literals that occur in type-params be normalized to the |
normalize type of Int literal type params (closes #41)
When is an
Core.Array{UInt8,1}
not aCore.Array{UInt8,1}
?Answer: When
Core.Array{UInt8,1}).uid
is not 27.How does it get that way?
idk exactly but it looks like when BSON deserializing
Dict{String, UInt8}
that was serializedon a 64 bit julia, on to a 32 bit julia,
BSON seems to be creating a new type with the same name in the same module.
but a different
uid
the true type.This is from invenia/JLSO.jl#11
and is why the AppVeyor 32 bit tests are failing (but are not showing as I said allow failures)
but a JSLO file is just a BSON file anyway.
WE:
On 32 bit system only.
Output:
I think a smaller working example can be created by running on a 64 bit computer
but I have not tested.
The text was updated successfully, but these errors were encountered: